DNS Gurus
Cached · just now
86/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 2
Let's Encrypt logo Let's Encrypt Report URI logo Report URI

Certificate Information

Subject
CN=status.merge.dev
Issuer
C=US, O=Let's Encrypt, CN=YR1
Valid From
September 02, 2026
Valid Until
December 01, 2026 54 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
31:16:E1:48:25:21:8C:95:A9:AF:C3:1F:B3:8C:E9:34:5E:13:90:AF:E7:63:D9:50:BE:F1:DC:BB:D6:77:F1:2A
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
Weak
max-age=0
Content-Security-Policy
Report URI logo
Basic
base-uri; block-all-mixed-content; frame-ancestors; +4 more Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • • 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

Subject Alternative Names

1 domain
status.merge.dev