Open
Cached
·
just now
83/100
SECURITY SCORE
Detected Technologies
Certificate Information
Subject
CN=bug2.onlyfans.com
Issuer
C=US, O=Amazon, CN=Amazon RSA 2048 M01
Valid From
November 12, 2025
Valid Until
December 11, 2026
186 days
Public Key
RSA
2048 bit
Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
79:7B:CD:F1:A8:10:F8:B4:1E:69:D6:05:41:D6:EA:69:4F:E7:8C:7C:BD:73:FA:4A:F8:7B:E5:FC:32:EC:92:40
Alternative Names
Security Configuration
TLS Protocols
TLS 1.3
Forward Secrecy
Supported
(Modern clients use PFS)
HTTP Security Headers
Status
Strict-Transport-Security
Present
max-age=31536000; includeSubdomains; preload
X-Frame-Options
Present
deny, SAMEORIGIN
X-Content-Type-Options
Present
nosniff, nosniff
Referrer-Policy
Missing
Not configured
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 Referrer-Policy header (recommended: strict-origin-when-cross-origin)
- • 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