DNS Gurus
Cached · just now
86/100 SECURITY SCORE

Detected Technologies

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

Certificate Information

Subject
CN=customer.buypass.no
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
April 24, 2026
Valid Until
July 23, 2026 80 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
C7:A3:7C:9A:61:48:06:8D:92:6E:8B:8C:FF:43:DB:8B:5B:B3:B7:70:B7:A1:F7:EF:08:35:ED:EC:FB:99:E3:07
Alternative Names
34 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
Present
max-age=259200
Content-Security-Policy
Missing
Not configured Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Missing
Not configured
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
  • • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • • Add Content-Security-Policy header to prevent XSS attacks
  • • Add X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • • 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
letsencrypt.org globalsign.com
Recommendations
  • • Consider using critical flag (flags=128) for stricter CAA enforcement
  • • Consider adding 'iodef' records to receive notifications about unauthorized certificate issuance attempts
  • • Consider adding 'issuewild' records to control wildcard certificate issuance