DNS Gurus
Cached · 4h ago
84/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 1
Let's Encrypt logo Let's Encrypt

Certificate Information

Subject
CN=www.apollographql.com
Issuer
C=US, O=Let's Encrypt, CN=E7
Valid From
March 16, 2026
Valid Until
June 14, 2026 39 days
Public Key
ECDSA 256 bit (P-256) Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
69:50:B7:87:78:E9:7D:AC:81:3C:12:B7:F5:14:63:52:E2:C4:DE:D8:B2:1A:40:4C:80:D2:EB:0E:5E:00:7C:49
Alternative Names
16 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
require-trusted-types-for; report-uri; object-src; +2 more Analyze
Content-Security-Policy-Report-Only
Weak
report-uri; frame-ancestors Analyze
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
origin
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 X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • • 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