DNS Gurus
Cached · 11m ago
92/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 2
Google Trust logo Google Trust PostHog logo PostHog

Certificate Information

Subject
CN=csvfile.tools
Issuer
C=US, O=Google Trust Services, CN=WE1
Valid From
November 03, 2026
Valid Until
February 01, 2027 82 days
Public Key
ECDSA 256 bit (P-256) Adequate
Signature Algorithm
ECDSA-SHA256
SHA-256 Fingerprint
55:5D:3B:AD:3A:E7:2F:02:E8:18:EC:54:06:AA:D7:5E:62:16:B2:6F:72:84:61:05:5B:CA:EE:32:90:A3:60:02
Alternative Names
3 domains

Security Configuration

TLS Protocols
TLS 1.0 TLS 1.1 TLS 1.2 TLS 1.3
Forward Secrecy
Supported (Modern clients use PFS)
Warnings
  • • TLS 1.1 is deprecated and should be disabled
  • • TLS 1.0 is deprecated and should be disabled

HTTP Security Headers

Status
Strict-Transport-Security
Good
max-age=63072000; includeSubDomains
Content-Security-Policy
PostHog logo
Basic
default-src; base-uri; connect-src; +8 more Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Present
camera=(), geolocation=(), microphone=()
Recommendations
  • • Consider adding 'preload' to HSTS for maximum security
  • • Improve CSP by adding more specific directives and removing 'unsafe-inline'

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