DNS Gurus
Cached · just now
89/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 7
Google Trust logo Google Trust Google Fonts logo Google Fonts Mapbox logo Mapbox Mixpanel logo Mixpanel Okta logo Okta Sentry logo Sentry Vidyard logo Vidyard

Certificate Information

Subject
CN=ci.com
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
February 21, 2026
Valid Until
May 22, 2026 40 days
Public Key
ECDSA 256 bit (P-256) Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
D7:1E:73:18:44:EB:8E:9A:2D:71:58:54:48:09:27:44:8B:09:52:B1:45:F7:E8:F0:C8:D0:E5:5F:CC:A1:A0: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=315360000; includeSubDomains
Content-Security-Policy
Weak
frame-ancestors Analyze
Content-Security-Policy-Report-Only
Google Fonts logo
Basic
default-src; connect-src; script-src; +5 more 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
  • • Significantly strengthen CSP directives
  • • 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
ci.com *.ci.com