Identity
89
C
crowdstrike.com
Posture Score: 73/100
Scanned May 17, 2026 at 8:19 PM UTC
Attack Surface
40
Reputation
91
Identity Findings
No CAA records found
No CAA records are configured. Any certificate authority can issue certificates for this domain.
💡 Add CAA records to restrict certificate issuance. Example: 0 issue "letsencrypt.org"
Void lookup: include:%{ir}.%{v}.%{d}.spf.has.pphosted.com
The mechanism include:%{ir}.%{v}.%{d}.spf.has.pphosted.com returns no records, wasting a DNS lookup.
💡 Remove mechanisms that reference non-existent domains.
ARC support not detected
No evidence of ARC (Authenticated Received Chain) support on MX servers. Forwarded messages may lose authentication.
💡 Consider enabling ARC signing on your mail servers to preserve authentication through forwarding.
Shared IP 148.163.148.77 used by multiple MX servers
The IP 148.163.148.77 is shared across 2 MX hostnames, reducing redundancy.
💡 Use unique IP addresses for each MX server for better redundancy.
Very low TTL on MX records: 271s
2 MX records have a TTL of 271s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on TXT records: 271s
46 TXT records have a TTL of 271s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on SPF record: 271s
The SPF record has a TTL of 271s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
Very low TTL on DMARC record: 271s
The DMARC record has a TTL of 271s or less (below 300s).
💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.
SPF record length OK (56 bytes)
SPF record is within safe DNS packet size limits.
DKIM records are valid
DKIM records found and validated for selectors: default, google
DKIM cryptographic configuration is compliant
No RFC 8301 compliance issues detected in DKIM key configuration.
DKIM key strength indicates modern key management
All DKIM keys use RSA-2048+ or Ed25519, consistent with current best practices.
All external report destinations authorized
External DMARC report destinations have valid authorization records per RFC 7489 §7.1.
Subdomains protected (sp=reject)
DMARC subdomain policy enforces quarantine or reject on unauthenticated subdomain mail.
MX records are valid
All MX records are properly configured.
MTA-STS and TLS-RPT are properly configured
MTA-STS policy is enforced and TLS reporting is configured.
TLS-RPT report destinations are reachable
All TLS-RPT rua= URIs point to resolvable domains.
BIMI record is valid
BIMI is properly configured with a valid logo and DMARC enforcement.
VMC URL is accessible
The BIMI VMC authority URL is reachable and returns a valid response.
Meets bulk sender authentication requirements
Domain has SPF, DKIM, and DMARC — meeting Google/Yahoo 2024 bulk sender requirements for email authentication.
SMTP security checks passed
No open relay, VRFY/EXPN, or banner disclosure issues detected.
SMTP RFC 5321 compliance checks passed
The mail server accepts postmaster@ and abuse@ and uses a valid FQDN in EHLO.
IPv6 readiness is good
IPv6 records are present and properly configured.
STARTTLS downgrade resistance is adequate
STARTTLS is supported with modern TLS and protected by MTA-STS and/or DANE.
NS delegation is properly configured
All nameservers are responsive, consistent, and properly secured.
DNS responses are consistent across all nameservers
All authoritative nameservers return consistent answers with proper AA flags.
DKIM2 not detected
No DKIM key record with v=2 was found across common selectors. DKIM2 is an emerging standard and not yet widely deployed.
DMARC alignment: adkim=r, aspf=r
DKIM alignment is relaxed, SPF alignment is relaxed.
DMARC failure reporting: fo=1
Failure reports generated when any authentication mechanism fails.
DMARCbis np tag absent
The DMARC record does not include the np (non-existent subdomain policy) tag. Consider adding np=reject to protect non-existent subdomains under DMARCbis.
Deprecated DMARCbis tags found: ri
The DMARC record contains tags deprecated in DMARCbis: ri. Consider removing these for forward compatibility.
DMARCbis psd tag absent
The DMARC record does not include the psd (public suffix domain) indicator. Consider adding psd=n to explicitly identify this as an organizational domain.
REQUIRETLS not advertised
The primary MX does not advertise REQUIRETLS (RFC 8689). This is an emerging standard — MTA-STS and DANE provide adequate TLS enforcement for most deployments.
No DANE/TLSA records found
DANE is not configured for any MX server. This is optional but provides strong certificate binding.
Open mail ports on mxa-00206402.gslb.pphosted.com
Detected open mail-related ports: 25
RFC 8058 one-click unsubscribe assessment
DKIM signing is configured. RFC 8058 compliance depends on List-Unsubscribe and List-Unsubscribe-Post headers being included in outbound messages and DKIM signatures.
MX IP network diversity
All MX IPs are in the same /16 network. Consider diversifying across networks for resilience.
SOA record parameters
Serial: 2404256563, Refresh: 10000s, Retry: 2400s, Expire: 604800s, Min TTL: 1800s
Attack Surface Findings
NSEC records enable zone walking
The domain uses NSEC records for DNSSEC authenticated denial of existence. NSEC records can be walked to enumerate all names in the zone, effectively disclosing the entire zone contents.
💡 Switch from NSEC to NSEC3 with opt-out to prevent zone enumeration. Use NSEC3 with a random salt and sufficient iterations.
Domain enumerability: high
The domain is highly enumerable. Zone transfers, NSEC zone walking, or a combination of factors make it easy to discover all DNS records.
💡 Restrict zone transfers, use NSEC3 instead of NSEC, consider wildcard certificates to reduce CT log exposure, and implement rate limiting on DNS queries.
Non-responsive IP for www.crowdstrike.com: 2606:4700::6810:b476
The subdomain www.crowdstrike.com resolves to 2606:4700::6810:b476 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6810:b476 is operational or remove the DNS record for www.crowdstrike.com.
Non-responsive IP for www.crowdstrike.com: 2606:4700::6810:b576
The subdomain www.crowdstrike.com resolves to 2606:4700::6810:b576 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6810:b576 is operational or remove the DNS record for www.crowdstrike.com.
Non-responsive IP for dev.crowdstrike.com: 2606:4700::6810:b576
The subdomain dev.crowdstrike.com resolves to 2606:4700::6810:b576 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6810:b576 is operational or remove the DNS record for dev.crowdstrike.com.
Non-responsive IP for dev.crowdstrike.com: 2606:4700::6810:b476
The subdomain dev.crowdstrike.com resolves to 2606:4700::6810:b476 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6810:b476 is operational or remove the DNS record for dev.crowdstrike.com.
Non-responsive IP for store.crowdstrike.com: 2606:4700::6810:b476
The subdomain store.crowdstrike.com resolves to 2606:4700::6810:b476 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6810:b476 is operational or remove the DNS record for store.crowdstrike.com.
Non-responsive IP for store.crowdstrike.com: 2606:4700::6810:b576
The subdomain store.crowdstrike.com resolves to 2606:4700::6810:b576 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6810:b576 is operational or remove the DNS record for store.crowdstrike.com.
Non-responsive IP for support.crowdstrike.com: 2606:4700::6810:b476
The subdomain support.crowdstrike.com resolves to 2606:4700::6810:b476 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6810:b476 is operational or remove the DNS record for support.crowdstrike.com.
Non-responsive IP for support.crowdstrike.com: 2606:4700::6810:b576
The subdomain support.crowdstrike.com resolves to 2606:4700::6810:b576 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6810:b576 is operational or remove the DNS record for support.crowdstrike.com.
Non-responsive IP for docs.crowdstrike.com: 2606:4700::6810:b576
The subdomain docs.crowdstrike.com resolves to 2606:4700::6810:b576 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6810:b576 is operational or remove the DNS record for docs.crowdstrike.com.
Non-responsive IP for docs.crowdstrike.com: 2606:4700::6810:b476
The subdomain docs.crowdstrike.com resolves to 2606:4700::6810:b476 which is not responding on ports 80 or 443. This may indicate a decommissioned server.
💡 Verify the server at 2606:4700::6810:b476 is operational or remove the DNS record for docs.crowdstrike.com.
NSEC used instead of NSEC3 (zone enumeration possible)
The domain uses NSEC records for authenticated denial of existence. NSEC allows zone walking.
💡 Migrate from NSEC to NSEC3 to prevent zone enumeration.
All MX records resolve correctly
No dangling MX records detected — all MX hostnames resolve to valid IP addresses.
Explicit MX records present
The domain has explicit MX records — no implicit A-record fallback delivery.
No internal information leakage detected
No non-routable IP addresses or internal references were found in public DNS records.
No email autodiscovery endpoints detected
No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.
10 subdomain(s) discovered for crowdstrike.com
Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.
0 certificate(s) found in CT logs
Certificate Transparency logs contain 0 certificate(s) for crowdstrike.com and its subdomains. Each certificate reveals subdomain names.
DNSSEC is enabled
DNSKEY and/or DS records are present, indicating DNSSEC is configured.
Reputation Findings
DMARC reports sent to URL shortener domain
DMARC aggregate or forensic reports contain sensitive authentication metadata. Sending them to URL shortener domains indicates misconfiguration or a compromised record.
💡 Change DMARC rua/ruf addresses to a domain you control.
HSTS enabled but missing preload directive on crowdstrike.com
Strict-Transport-Security: max-age=31536000; includeSubDomains
💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.
Not listed on any DNS blacklists
Domain and MX IPs checked against 55 DNSBLs — no listings found.
security.txt present
Found security.txt at https://crowdstrike.com/.well-known/security.txt.
TLS certificate valid for 82 days
Certificate for crowdstrike.com expires on 2026-08-08.
Certificate issued by WE1
The certificate for crowdstrike.com is issued by a third-party CA.
Signature algorithm: ecdsa-with-sha256
The certificate for crowdstrike.com uses an acceptable signature algorithm.
ECC key: 256 bits
The certificate for crowdstrike.com uses an adequate ECC key of 256 bits.
SCTs present in certificate
The certificate for crowdstrike.com contains Signed Certificate Timestamps.
No weak ciphers detected
No known weak cipher suites detected on crowdstrike.com.
No disposable email provider MX records
MX records for crowdstrike.com do not match known disposable email provider patterns.
No wildcard MX records
No wildcard MX records detected for crowdstrike.com.
TLD has good reputation
The .com TLD is not on known abuse watchlists.
MX records point to stable infrastructure
No MX records point to known dynamic DNS service domains.
Strong TLS configuration on primary MX
Primary MX (mxa-00206402.gslb.pphosted.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.
SMTP banner from hosted mail provider
The MX (mxa-00206402.gslb.pphosted.com) is a hosted mail service. Banner alignment is managed by the provider and not actionable by the domain owner.
Google Safe Browsing DNS check — no flag detected
DNS-based Safe Browsing lookup returned no results. Full verification requires the Google Safe Browsing API key.
Abuse contacts found for MX IPs
Abuse contact information retrieved via abusix.org DNS lookup.
PhishTank — API key required
PhishTank phishing database check requires an API key.
Sender Score — API key required
Sender Score reputation check requires an API key.
Cisco Talos — API key required
Cisco Talos IP reputation check requires an API key.
Could not connect to webmail.crowdstrike.com
HTTPS request to https://webmail.crowdstrike.com failed or timed out.
WHOIS lookup failed
Could not retrieve WHOIS data for crowdstrike.com.
Could not determine domain age
WHOIS creation date could not be parsed for crowdstrike.com.
Bulletproof Hosting Detection — API key required
Checking IPs against known bulletproof hosting providers requires a threat intelligence API key.
Threat Intelligence Feeds — API key required
Checking domain against threat intelligence feeds requires API keys (e.g., VirusTotal, AbuseIPDB).
Typosquat detected: rowdstrike.com (has MX!), cowdstrike.com (has MX!), crwdstrike.com (has MX!), crodstrike.com (has MX!), crowstrike.com (has MX!)
29 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 29. Domains with MX records can send and receive email, making them high-risk phishing vectors.
Dependency Chains
DMARC Authentication Chain (SPF)
DMARC uses SPF to verify that emails come from authorized servers
SPF Record
SPF record found and configured
→
DMARC Policy
DMARC policy: reject
DMARC Authentication Chain (DKIM)
DMARC uses DKIM to verify that emails have not been tampered with
DKIM Signature
DKIM signature configured
→
DMARC Policy
DMARC policy: reject
Mail Server Identity: mxa-00206402.gslb.pphosted.com
PTR record proves mail server legitimacy
MX: mxa-00206402.gslb.pphosted.com
Mail server at 148.163.148.77
→
PTR Record
Reverse DNS: mx0a-00206402.pphosted.com
Mail Server Identity: mxb-00206402.gslb.pphosted.com
PTR record proves mail server legitimacy
MX: mxb-00206402.gslb.pphosted.com
Mail server at 148.163.152.16
→
PTR Record
Reverse DNS: mx0b-00206402.pphosted.com
Mail Server Reputation: mxa-00206402.gslb.pphosted.com
RBL check ensures server is not blacklisted
MX: mxa-00206402.gslb.pphosted.com
Mail server at 148.163.148.77
→
RBL Status
Not blacklisted
Mail Server Reputation: mxb-00206402.gslb.pphosted.com
RBL check ensures server is not blacklisted
MX: mxb-00206402.gslb.pphosted.com
Mail server at 148.163.152.16
→
RBL Status
Not blacklisted
Enforced Encryption Chain
MTA-STS enforces TLS encryption to prevent man-in-the-middle attacks
TLS Support
Mail servers support TLS encryption
→
MTA-STS Policy
Mode: enforce
Brand Identity Chain
BIMI displays your logo in email clients, but requires DMARC enforcement
DMARC Enforcement
DMARC policy: reject
→
BIMI Record
Brand logo configured
TLS Monitoring Chain
TLS-RPT provides reports about TLS connection failures
TLS Support
Mail servers support TLS encryption
→
TLS-RPT Reporting
TLS failure reporting configured
Security Checks
MX Records
✓
SPF Record
✓
DKIM Record
✓
DMARC Policy
✓
BIMI Record
✓
CAA Records
✗
DNSSEC
✓
MTA-STS
✓
TLS-RPT
✓
Embed Badge
Display your domain's security grade on your website or README:
<img src="https://scan.ractermx.com/badge/crowdstrike.com.svg" alt="Email Security Grade">
Want to re-scan this domain for updated results?
Scan crowdstrike.com Again