DNS Gurus
Cached · just now
82/100 SECURITY SCORE

Detected Technologies

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

Certificate Information

Subject
CN=status.bottomline.com
Issuer
C=US, O=Let's Encrypt, CN=R12
Valid From
April 03, 2026
Valid Until
July 02, 2026 54 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
62:9D:26:0D:71:14:90:CE:E9:44:60:D1:98:F8:83:E9:FD:F3:48:E2:56:CA:2F:F9:66:CF:F3:77:94:62:6C:A9
Alternative Names
17 domains

Security Configuration

TLS Protocols
TLS 1.2
Forward Secrecy
Limited (Check cipher configuration)
Warnings
  • • TLS 1.3 is not supported (recommended)

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
Good
strict-origin-when-cross-origin
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
  • • 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