DNS Gurus
Cached · just now
92/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 1
Google Trust logo Google Trust

Certificate Information

Subject
CN=www.telesign.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
April 18, 2026
Valid Until
July 18, 2026 77 days
Public Key
ECDSA 256 bit (P-256) Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
05:09:6B:D1:FB:DF:AC:4A:C6:72:23:A0:41:DE:76:AA:34:A1:38:2B:6E:44:9B:51:CF:77:3F:C9:8C:D4:F0:B6
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
Excellent
max-age=63072000; includeSubDomains; preload
Content-Security-Policy
Weak
upgrade-insecure-requests; block-all-mixed-content 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
Present
geolocation=(), microphone=(), camera=()
Recommendations
  • • Significantly strengthen CSP directives

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
www.telesign.com