Cached · just now
82/100 SECURITY SCORE

Certificate Information

Subject
C=DK, L=Kongens Lyngby, O=DTU/DeiC Forskningsnettet, CN=deic.dk
Issuer
C=GR, O=Hellenic Academic and Research Institutions CA, CN=GEANT TLS RSA 1
Valid From
October 28, 2026
Valid Until
May 15, 2027 184 days
Public Key
RSA 4096 bit Strong
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
69:C3:29:CD:A6:00:37:FB:96:FC:1C:F9:5C:60:06:FC:8D:03:F8:CA:AD:05:80:8A:45:37:60:BD:1C:FC:7D:E8
Alternative Names

Security Configuration

TLS Protocols
TLS 1.2 TLS 1.3
Forward Secrecy
Supported (Modern clients use PFS)

HTTP Security Headers

Status
Strict-Transport-Security
Missing
Not configured
Content-Security-Policy
Missing
Not configured Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • • Add Strict-Transport-Security header with max-age of at least 1 year
  • • Add Content-Security-Policy header to prevent XSS attacks
  • • 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

Subject Alternative Names

2 domains