DNS Gurus
Cached · just now
92/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 4
Microsoft Entra ID logo Microsoft Entra ID AzureFrontDoor logo AzureFrontDoor Microsoft Clarity logo Microsoft Clarity Microsoft 365 logo Microsoft 365

Certificate Information

Subject
C=US, ST=WA, L=Redmond, O=Microsoft Corporation, CN=odc.edog.officeapps.live.com
Issuer
C=US, O=Microsoft Corporation, CN=Microsoft TLS G2 RSA CA OCSP 16
Valid From
February 17, 2026
Valid Until
February 12, 2027 311 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA384-RSA
SHA-256 Fingerprint
A0:32:1C:55:55:54:E8:59:D7:09:18:60:2B:03:58:53:39:84:E7:39:AE:66:44:7C:7F:3E:59:A6:55:8D:67:94
Alternative Names
2 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
Microsoft Entra ID logo
Good
default-src; base-uri; script-src; +13 more Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
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
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