SSL Verification Bypassed

The server's SSL certificate could not be verified. The analysis was completed using insecure mode. Data may be less reliable.

Reason:

Hostname Mismatch - certificate is issued for adomian.pilgrimagetrackclub.com, assume.pilgrimagetrackclub.com, consequences.pilgrimagetrackclub.com, cook.pilgrimagetrackclub.com, decade.pilgrimagetrackclub.com, discount.pilgrimagetrackclub.com, favorable.pilgrimagetrackclub.com, gahuza.pilgrimagetrackclub.com, german.pilgrimagetrackclub.com, not for beta.sharewithclients.com

81/100 SECURITY SCORE

Certificate Information

Subject
CN=pilgrimagetrackclub.com
Issuer
C=US, O=Let's Encrypt, CN=R13
Valid From
January 21, 2026
Valid Until
April 21, 2026 64 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
23:A3:1C:97:18:DC:45:FA:18:1A:ED:43:8E:4B:7A:B4:3B:CF:B7:27:48:F4:8D:8E:9A:E6:19:BC:AE:F1:B6:7B
Alternative Names

Security Configuration

TLS Protocols
TLS 1.2 TLS 1.3
Forward Secrecy
Supported (Modern clients use PFS)

HTTP Security Headers

Status
Strict-Transport-Security
Missing
Not configured
Content-Security-Policy
Missing
Not configured
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Missing
Not configured
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
  • 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