DNS Gurus
Cached · just now
78/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 1
DigiCert logo DigiCert

Certificate Information

Subject
C=CA, ST=Ontario, L=TORONTO, O=FIDELITY INVESTMENTS CANADA ULC, CN=www.wealth.fidelity.ca
Issuer
C=US, O=DigiCert Inc, CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid From
June 04, 2025
Valid Until
June 16, 2026 41 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
38:62:C2:6A:46:31:B6:02:35:48:0A:78:F6:5E:F7:5C:9B:67:45:BE:B8:7C:B0:15:35:FE:4E:E6:10:9A:41:E5
Alternative Names
28 domains

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=63072000; includeSubdomains;
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
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 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