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

Certificate Information

Subject
C=US, ST=New Hampshire, L=Portsmouth, O=Gmo Globalsign, Inc., CN=atlas.globalsign.com
Issuer
C=BE, O=GlobalSign nv-sa, CN=GlobalSign Atlas R3 OV TLS CA 2025 Q2
Valid From
June 10, 2025
Valid Until
July 12, 2026 244 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
31:1B:65:CA:CD:AC:71:DA:CD:ED:C6:3D:56:04:9A:10:7A:68:E5:9C:FB:BF:24:67:39:B8:7D:76:98:59:4E:30
Alternative Names
1 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=86400; includeSubDomains
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • • Add Content-Security-Policy header to prevent XSS attacks
  • • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • • Add X-Content-Type-Options: nosniff
  • • 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
Configured (Restricts certificate issuance)
Current Issuer
Authorized (Matches CAA policy)
Authorized CAs
amazonaws.com globalsign.com
Incident Reporting
Recommendations
  • • Consider using critical flag (flags=128) for stricter CAA enforcement
  • • Consider adding 'issuewild' records to control wildcard certificate issuance

Subject Alternative Names

1 domain
atlas.globalsign.com