DNS Gurus
Cached · just now
86/100 SECURITY SCORE

Certificate Information

Subject
C=US, ST=WA, L=Redmond, O=Microsoft Corporation, CN=bat.bing.com
Issuer
C=US, O=Microsoft Corporation, CN=Microsoft Azure RSA TLS Issuing CA 04
Valid From
February 07, 2026
Valid Until
August 06, 2026 166 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA384-RSA
SHA-256 Fingerprint
46:84:54:F0:C8:1F:81:9A:F1:36:6D:C0:72:F6:E9:D4:AF:40:BC:2D:A8:9C:F0:19:6A:C1:E1:DF:80:DB:FD:25
Alternative Names
27 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
Present
max-age=1209600; includeSubDomains; preload
Content-Security-Policy
Basic
block-all-mixed-content; connect-src; default-src; +5 more Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Good
sameorigin
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • • Improve CSP by adding more specific directives and removing 'unsafe-inline'
  • • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
  • • 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