DNS Gurus
Cached · just now
81/100 SECURITY SCORE

Certificate Information

Subject
C=US, ST=WA, L=Redmond, O=Microsoft Corporation, CN=dev.microsoftservicegraph.io
Issuer
C=US, O=Microsoft Corporation, CN=Microsoft Azure RSA TLS Issuing CA 04
Valid From
July 04, 2025
Valid Until
December 31, 2025 2 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA384-RSA
SHA-256 Fingerprint
3D:5E:32:CB:75:AA:9F:25:9C:BD:7D:4C:63:23:07:7E:90:BC:C3:BB:03:64:16:30:79:E7:D4:8C:A8:1B:CA:38
Alternative Names
2 domains

Security Configuration

TLS Protocols
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
frame-ancestors
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • • Consider adding 'preload' to HSTS for maximum security
  • • Significantly strengthen CSP directives
  • • 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