DNS Gurus
Cached · just now
89/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 6
Let's Encrypt logo Let's Encrypt Active incidents CARTO logo CARTO Contentful logo Contentful GitHub logo GitHub Google Fonts logo Google Fonts Matomo logo Matomo

Certificate Information

Subject
CN=dfinity.network
Issuer
C=US, O=Let's Encrypt, CN=E7
Valid From
May 02, 2026
Valid Until
July 31, 2026 80 days
Public Key
ECDSA 256 bit (P-256) Adequate
Signature Algorithm
ECDSA-SHA384
SHA-256 Fingerprint
7D:59:60:38:B2:F5:47:9F:FE:75:8E:F3:05:86:6B:48:7B:41:3F:E0:B6:E5:06:0A:8B:00:1D:86:00:29:FE:D0
Alternative Names
3 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
Missing
Not configured
Content-Security-Policy
GitHub logo
Basic
default-src; script-src; style-src; +12 more Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Present
geolocation=(self)
Recommendations
  • • Add Strict-Transport-Security header with max-age of at least 1 year
  • • 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