DNS Gurus
Cached · just now
84/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 1
Let's Encrypt logo Let's Encrypt

Certificate Information

Subject
CN=123formbuilder.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
April 08, 2026
Valid Until
July 07, 2026 67 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
43:AC:56:2B:B0:3F:DE:F0:F0:AA:33:2C:A9:A4:EB:23:99:49:F4:2F:63:7B:39:4D:27:F7:F1:D2:D9:06:37:A8
Alternative Names
7 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
Basic
default-src; worker-src; script-src; +7 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
Missing
Not configured
Permissions-Policy
Missing
Not configured
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'
  • • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • • 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
Configured (Restricts certificate issuance)
Current Issuer
Authorized (Matches CAA policy)
Authorized CAs
amazon.com letsencrypt.org
Incident Reporting
Recommendations
  • • Consider using critical flag (flags=128) for stricter CAA enforcement
  • • Consider adding 'issuewild' records to control wildcard certificate issuance