DNS Gurus
Open Cached · just now
92/100 SECURITY SCORE

Certificate Information

Subject
C=US, ST=WA, L=Redmond, O=Microsoft Corporation, CN=m365.cloud.microsoft
Issuer
C=US, O=Microsoft Corporation, CN=Microsoft Azure RSA TLS Issuing CA 07
Valid From
October 29, 2025
Valid Until
April 27, 2026 175 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA384-RSA
SHA-256 Fingerprint
89:50:B3:A0:BE:29:B5:4C:54:4A:96:05:99:38:22:D4:0C:82:9F:6A:A7:5F:85:45:85:B1:F5:7B:1A:3F:01:3F
Alternative Names
20 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
Good
default-src; base-uri; script-src; +12 more
X-Frame-Options
Good
SAMEORIGIN
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
  • • Strengthen CSP by removing 'unsafe-eval'
  • • Consider adding Permissions-Policy to control browser features

CAA Records (Certificate Authority Authorization)

CAA Records
Configured (Restricts certificate issuance)
Current Issuer
Not Authorized (Potential misconfiguration)
Authorized CAs
globalsign.com microsoft.com digicert.com dtrust.de entrust.net
Incident Reporting
CAA Issues
  • • CRITICAL: Current certificate issuer 'C=US, O=Microsoft Corporation, CN=Microsoft Azure RSA TLS Issuing CA 07' is NOT authorized by CAA records. Authorized CAs: globalsign.com, microsoft.com, digicert.com, dtrust.de, entrust.net
Recommendations
  • • Consider using critical flag (flags=128) for stricter CAA enforcement
  • • You have authorized 5 CAs - consider limiting to only the CAs you actively use
  • • Consider adding 'issuewild' records to control wildcard certificate issuance