DNS Gurus
Cached · just now
84/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 1
Google Trust logo Google Trust

Certificate Information

Subject
CN=readmessl.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
June 28, 2026
Valid Until
September 26, 2026 61 days
Public Key
ECDSA 256 bit (P-256) Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
A9:9D:12:FF:12:D0:3F:9E:72:3B:CA:57:97:65:8C:DD:6E:0D:56:56:8D:70:1F:AA:FA:D1:8B:F6:06:08:EB:C0
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
Missing
Not configured
Content-Security-Policy
Missing
Not configured Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Missing
Not configured
Referrer-Policy
Present
same-origin
Permissions-Policy
Missing
Not configured
Recommendations
  • • Add Strict-Transport-Security header with max-age of at least 1 year
  • • Add Content-Security-Policy header to prevent XSS attacks
  • • Add X-Content-Type-Options: nosniff
  • • 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
amazontrust.com comodoca.com digicert.com letsencrypt.org pki.goog ; cansignhttpexchanges=yes ssl.com
Wildcard CAs
comodoca.com digicert.com letsencrypt.org pki.goog ; cansignhttpexchanges=yes ssl.com
Recommendations
  • • Consider using critical flag (flags=128) for stricter CAA enforcement
  • • You have authorized 6 CAs - consider limiting to only the CAs you actively use
  • • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts

Subject Alternative Names

2 domains
readmessl.com *.readmessl.com