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

Certificate Information

Subject
C=CA, ST=British Columbia, L=Vancouver, O=Global Relay Communications Inc., CN=developers.globalrelay.com
Issuer
C=US, O=DigiCert Inc, CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid From
January 13, 2025
Valid Until
February 13, 2026 92 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
4E:55:8C:AB:2D:18:A2:76:A5:E5:D6:0A:8B:19:06:11:2A:F1:CE:12:F6:3A:D5:39:AE:D4:CB:C6:B3:46:96:09
Alternative Names
4 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
Missing
Not configured
Content-Security-Policy
Basic
connect-src; default-src; child-src; +8 more
X-Frame-Options
Present
ALLOW-FROM controlcenter.globalrelay.com compliance.login.globalrelay.com global-relay-staging.go-vip.net developers.globalrelay.com dev-developers.globalrelay.com preprod-developers.globalrelay.com
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • • Add Strict-Transport-Security header with max-age of at least 1 year
  • • 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