DNS Gurus
Cached · just now
89/100 SECURITY SCORE

Certificate Information

Subject
CN=crowdstrike.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
January 12, 2026
Valid Until
April 12, 2026 89 days
Public Key
ECDSA 256 bit (P-256) Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
79:76:0E:36:24:E5:E3:F2:8C:4A:13:4B:7A:AD:70:F9:4D:9E:87:B4:01:B3:48:AE:6E:FE:51:0E:B0:FD:B5:F5
Alternative Names
4 domains

Security Configuration

TLS Protocols
TLS 1.2 TLS 1.3
Forward Secrecy
Supported (Modern clients use PFS)

HTTP Security Headers

Status
Strict-Transport-Security
Good
max-age=31536000; includeSubDomains
Content-Security-Policy
Weak
upgrade-insecure-requests; report-uri
X-Frame-Options
Present
ALLOW-FROM https://crowdstrike.pathfactory.com https://crowdstrike.com https://www.crowdstrike.co.uk https://go.crowdstrike.com https://store.crowdstrike.com
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
  • • Consider adding 'preload' to HSTS for maximum security
  • • Significantly strengthen CSP directives
  • • Consider adding Permissions-Policy to control browser features

CAA Records (Certificate Authority Authorization)

CAA Records
Not Configured (Any CA can issue certificates)
CAA Issues
  • • No CAA records configured - any CA can issue certificates
Recommendations
  • • Implement CAA records to restrict which CAs can issue certificates for your domain
  • • This adds an extra layer of security against unauthorized certificate issuance
  • • Example: Add CAA record 'example.com. CAA 0 issue "letsencrypt.org"'
  • • Consider adding 'iodef' record to receive security incident reports