DNS Gurus
Cached · just now
89/100 SECURITY SCORE

Detected Technologies

See all in URL Inspect 1
Sectigo logo Sectigo

Certificate Information

Subject
UNKNOWN=09231974, UNKNOWN={:asn1_OPENTYPE, <<19, 2, 71, 66>>}, UNKNOWN={:asn1_OPENTYPE, <<19, 20, 80, 114, 105, 118, 97, 116, 101, 32, 79, 114, 103, 97, 110, 105, 122, 97, 116, 105, 111, 110>>}, C=GB, ST=London, O=HSBC Group Management Services Limited, CN=hsbcnet.com
Issuer
C=GB, O=Sectigo Limited, CN=Sectigo Public Server Authentication CA EV R36
Valid From
September 10, 2026
Valid Until
March 27, 2027 171 days
Public Key
RSA 2048 bit Adequate
Signature Algorithm
SHA256-RSA
SHA-256 Fingerprint
67:9C:69:75:73:1E:B4:E9:51:0F:AB:0A:2E:54:65:45:CD:55:88:65:29:E0:2D:85:3F:EA:AE:AC:6C:8F:B1:76
Alternative Names
28 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
Excellent
max-age=31536000 ; includeSubDomains ; preload
Content-Security-Policy
Missing
Not configured Analyze
Content-Security-Policy-Report-Only
Missing
Not configured Analyze
X-Frame-Options
Good
SAMEORIGIN
X-Content-Type-Options
Good
nosniff
Referrer-Policy
Good
strict-origin-when-cross-origin
Permissions-Policy
Missing
Not configured
Recommendations
  • • Add Content-Security-Policy header to prevent XSS attacks
  • • 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