DNS Gurus
Cached · just now
84/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 6
Let's Encrypt logo Let's Encrypt Active incidents YouTube logo YouTube Calendly logo Calendly Helpjuice logo Helpjuice HubSpot logo HubSpot Loom logo Loom

Certificate Information

Subject
CN=sdui.app
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
March 05, 2026
Valid Until
June 03, 2026 21 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
2C:4F:22:62:1E:A1:F2:66:DA:BF:54:BB:98:B4:49:BA:2E:F7:62:12:C9:30:F2:5D:9D:89:03:18:CE:A3:C6:CE
Alternative Names
5 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
YouTube logo
Good
default-src; connect-src; frame-src; +10 more Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Present
same-origin
Permissions-Policy
Present
camera=(self), microphone=(self)
Recommendations
  • • Add Strict-Transport-Security header with max-age of at least 1 year
  • • Strengthen CSP by removing 'unsafe-eval'
  • • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking

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