Cached · just now
75/100 SECURITY SCORE

Detected Technologies

Certificate Information

Subject
C=US, ST=New York, O=Fox Corporation, CN=fox.ai
Issuer
C=CA, O=Entrust Limited, CN=Entrust OV TLS Issuing RSA CA 2
Valid From
July 22, 2026
Valid Until
February 05, 2027 182 days
Public Key
RSA 3072 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
7B:95:69:E5:16:19:38:63:ED:28:73:42:78:7A:48:D9:37:15:46:29:8E:E1:3B:E8:FB:1C:CC:49:0F:40:B5:E3
Alternative Names

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
Present
max-age=15552000
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
Missing
Not configured
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 X-Frame-Options: DENY or SAMEORIGIN to prevent clickjacking
  • Add X-Content-Type-Options: nosniff
  • 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