DNS Gurus
Cached · just now
89/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 7
Let's Encrypt logo Let's Encrypt Active incidents Facebook logo Facebook Google Analytics logo Google Analytics Google API JS Client logo Google API JS Client Google Search logo Google Search Google Static File Front End logo Google Static File Front End Google Cloud logo Google Cloud

Certificate Information

Subject
CN=10053.sites.syca.nl
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
April 08, 2026
Valid Until
July 07, 2026 58 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
85:BE:60:3C:19:F1:42:8C:E0:97:0F:07:4F:EF:64:B0:29:E9:79:B4:F9:0C:B6:B3:72:76:67:1C:7C:33:BB:28
Alternative Names
4 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
Present
max-age=31536000; preload
Content-Security-Policy
Google Analytics logo
Basic
script-src; object-src Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Missing
Not configured
Recommendations
  • • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • • Improve CSP by adding more specific directives and removing 'unsafe-inline'
  • • 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