DNS Gurus
Cached · just now
92/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 7
AWS CloudFront logo AWS CloudFront Google Trust logo Google Trust Canny logo Canny Cloudflare Web Analytics logo Cloudflare Web Analytics Google Conversion Tracking logo Google Conversion Tracking Intercom logo Intercom jQuery logo jQuery

Certificate Information

Subject
CN=test.io
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
March 25, 2026
Valid Until
June 23, 2026 46 days
Public Key
ECDSA 256 bit (P-256) Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
F8:C6:28:D5:56:F4:DA:6D:94:F1:70:30:62:10:6B:08:19:A3:0E:D8:48:24:EA:E5:0C:6E:B9:8A:E3:2C:11:53
Alternative Names
2 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
Good
max-age=31536000; includeSubDomains
Content-Security-Policy
AWS CloudFront logo
Good
default-src; script-src; style-src; +7 more Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
  • • Consider adding 'preload' to HSTS for maximum security
  • • Strengthen CSP by removing 'unsafe-eval'
  • • 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

2 domains
test.io *.test.io