DNS Gurus
Cached · just now
81/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 1
Sectigo logo Sectigo

Certificate Information

Subject
C=DE, ST=Rheinland-Pfalz, O=1&1 Telecommunication SE, CN=*.yourfone-partner.de
Issuer
C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication CA OV R36
Valid From
October 22, 2025
Valid Until
October 22, 2026 80 days
Public Key
RSA 4096 bit Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
35:A8:55:76:20:1C:67:43:19:BA:9D:95:14:1C:71:8C:9A:B4:47:89:29:16:36:8E:E1:1B:B3:9B:67:4B:43:69
Alternative Names
3 domains

Security Configuration

TLS Protocols
TLS 1.1 TLS 1.2
Forward Secrecy
Limited (Check cipher configuration)
Warnings
  • • TLS 1.3 is not supported (recommended)
  • • TLS 1.1 is deprecated and should be disabled

HTTP Security Headers

Status
Strict-Transport-Security
Present
max-age=15552001; includeSubDomains
Content-Security-Policy
Weak
frame-ancestors Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Excellent
DENY
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • • Significantly strengthen CSP directives
  • • Add Referrer-Policy header (recommended: strict-origin-when-cross-origin)
  • • 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