DNS Gurus
Open Cached · just now
85/100 SECURITY SCORE

Certificate Information

Subject
C=US, ST=California, L=Palo Alto, O=Houzz Inc., CN=*.houzz.com
Issuer
C=BE, O=GlobalSign nv-sa, CN=GlobalSign Atlas R3 OV TLS CA 2025 Q2
Valid From
June 26, 2025
Valid Until
July 28, 2026 257 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
10:89:93:26:70:3B:6B:09:15:20:5A:10:E2:26:0B:B9:CB:F6:5B:C1:B3:AE:52:FF:FF:D9:F2:16:45:F6:E4:C7
Alternative Names
74 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=31536000; includeSubdomains; preload
Content-Security-Policy
Weak
frame-ancestors
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
Permissions-Policy
Missing
Not configured
Recommendations
  • • Increase HSTS max-age to at least 1 year and add includeSubDomains
  • • Significantly strengthen CSP directives
  • • 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