Back to results

Digital exposure report

hsbc.com

High exposure. Significant weaknesses put the brand, customers and email at risk.

Scanned: 2026-11-15 19:22 UTC

Partial coverage: the score is based on 52% of applicable check weight. 8 unverified check(s) are excluded, not counted as failures.

D
62/100

What to do first

  1. 1.

    Send visitors to the secure version of your site

    Visitors who type your address without https may stay on an unprotected connection.

    Who can fix it: Your web host

    How to verify after the fix

    curl -sI http://hsbc.com/ | grep -iE "^(HTTP|location)"
  2. 2.

    Turn on DNS signing for your domain

    Signing helps resolvers detect forged answers about your domain.

    Who can fix it: Your domain registrar or DNS provider

    How to verify after the fix

    dig +short DS hsbc.com

A starting point, not a security guarantee.

What this grade means

Tested hostname
hsbc.com
Website request
GET https://hsbc.com/(no HTTPS response)
Scan time
2026-11-15 19:22:34 UTC
Grading method
Version 2How grading works
Unverified or excluded checks
  • HTTPS available · Unverified
  • SSL/TLS certificate validity · Unverified
  • HSTS — enforce encryption in the browser · Unverified
  • CSP — protection from script injection · Unverified
  • Clickjacking protection · Unverified
  • X-Content-Type-Options · Unverified
  • Referrer-Policy · Unverified
  • Permissions-Policy · Unverified

This is a snapshot of the public configuration checks listed in this report. It does not verify the site's owner, business legitimacy, application security, or absence of vulnerabilities. It is not a security certification.

Score by category

Email security29/30Spoofing email from this domain is hard.
Encryption & certificate0/7Browsing to the site is not properly protected by encryption.
Browser protections—Nothing in this category could be verified from public data.
DNS infrastructure3/15The domain's infrastructure lacks basic protections.

Fix priorities

  1. 1.HighHTTP → HTTPS redirect · Hardening gap+13
  2. 2.MediumDNSSEC — signed DNS records · Hardening gap+13
  3. 3.LowCAA — who may issue certificates · Hardening gap+10

To verify

Couldn't be confirmed from public data, so excluded from the score. Checking them clarifies your posture; it doesn't guarantee a score change.

  • HTTPS available
  • SSL/TLS certificate validity
  • CSP — protection from script injection
  • HSTS — enforce encryption in the browser
  • Clickjacking protection
  • X-Content-Type-Options
  • Referrer-Policy
  • Permissions-Policy

Findings

SPF — who may send mail for the domain

Passed · Severity: OK · 9/10

An authorized sender list is defined; mail from other servers is flagged as suspicious.

~all (softfail) — acceptable when combined with enforced DMARC. 6 of 10 DNS lookups.

Source data: DNS TXT hsbc.com
v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com include:spf-00299f02.pphosted.com include:spf1.hsbc.com include:spf2.hsbc.com include:spf3.hsbc.com include:spf-002f0603.pphosted.com ~all
$ dig +short TXT hsbc.com
Documentation: RFC 7208 — SPF (https://www.rfc-editor.org/rfc/rfc7208) · M3AAWG — Email Authentication Best Practices (https://www.m3aawg.org/sites/default/files/m3aawg-email-authentication-recommended-best-practices-09-2020.pdf)

DMARC — anti-spoofing policy

Passed · Severity: OK · 15/15

Forged email in the company's name is blocked by mail servers.

Policy p=reject.

Source data: DNS TXT _dmarc.hsbc.com
v=DMARC1; p=reject; fo=1; ri=3600; rua=mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com
$ dig +short TXT _dmarc.hsbc.com
Documentation: RFC 7489 — DMARC (https://www.rfc-editor.org/rfc/rfc7489) · dmarc.org — FAQ (https://dmarc.org/resources/frequently-asked-questions/)

DKIM — digital signature on email

Passed · Severity: OK · 5/5

A DKIM public key is published. On its own this doesn't prove outgoing mail is signed or aligned with your From domain.

DKIM public key found for selector: google. Confirm signing with dkim=pass in a sent message's Authentication-Results.

Source data: DNS TXT <selector>._domainkey.hsbc.com
google._domainkey: v=DKIM1;k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnmgxMS9YsYbSG5XoJ1+QCpd5h6MZg…
$ dig +short TXT google._domainkey.hsbc.com
Documentation: RFC 6376 — DKIM (https://www.rfc-editor.org/rfc/rfc6376) · M3AAWG — Email Authentication Best Practices (https://www.m3aawg.org/sites/default/files/m3aawg-email-authentication-recommended-best-practices-09-2020.pdf)

MX — inbound mail routing

Passed · Severity: OK · unscored

Mail exchangers are published for the domain.

2 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.

Source data: DNS MX hsbc.com
10 mxb-00299f02.gslb.pphosted.com
10 mxa-00299f02.gslb.pphosted.com
$ dig +short MX hsbc.com
Documentation: RFC 7505 — Null MX (https://www.rfc-editor.org/rfc/rfc7505) · RFC 5321 §5.1 — Locating the target host (https://www.rfc-editor.org/rfc/rfc5321#section-5.1)

HTTPS available

Unverified · Severity: OK · Not scored

HTTPS couldn't be confirmed: the request timed out or the connection failed. This isn't treated as a security failure.

Requesting https://hsbc.com/ didn't complete (TimeoutError: The operation was aborted due to timeout). Timeouts and transport errors may be transient; the check is excluded from the score.

Source data: HTTPS GET https://hsbc.com/
TimeoutError: The operation was aborted due to timeout
$ curl -svI https://hsbc.com/ 2>&1 | grep -E "SSL|HTTP|expire"
Documentation: OWASP — Transport Layer Security Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Transport_Layer_Security_Cheat_Sheet.html) · Mozilla — Server Side TLS (https://wiki.mozilla.org/Security/Server_Side_TLS)

HTTP → HTTPS redirect

Failed · Severity: High · Hardening gap · 0/7

The site is also reachable over an unencrypted connection, so data may travel in plain text on public networks.

http://hsbc.com/ returned HTTP 301 without redirecting to https:// (Location: http://www.hsbc.com/).

Source data: HTTP GET http://hsbc.com/ (redirects not followed)
HTTP 301
Location: http://www.hsbc.com/
$ curl -sI http://hsbc.com/ | grep -iE "^(HTTP|location)"
Fix recommendation (effort: Easy)
  1. Set up a permanent (301) redirect from every HTTP request to HTTPS on the server or CDN.
  2. Then add an HSTS header.
server {
  listen 80;
  server_name hsbc.com www.hsbc.com;
  return 301 https://$host$request_uri;
}

Safety: This change is made on your server. Make sure HTTPS works first, otherwise the site won't load.

Documentation: OWASP — Transport Layer Security Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Transport_Layer_Security_Cheat_Sheet.html) · RFC 6797 — HSTS (https://www.rfc-editor.org/rfc/rfc6797)

SSL/TLS certificate validity

Unverified · Severity: OK · Not scored

The certificate couldn't be checked live because the HTTPS connection didn't complete. CT log data alone isn't used to score validity or expiry.

No live TLS evidence was obtained. CT entries are shown as context only. Not scored.

Source data: Certificate Transparency logs (certspotter) for hsbc.com
CT logs (context only, not scored):
Issuer: Sectigo
Valid from: 2026-10-27
Valid until: 2027-05-13
Names: hsbc.com, www.hsbc.com
Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect hsbc.com:443 -servername hsbc.com 2>/dev/null | openssl x509 -noout -issuer -dates
Documentation: Certificate Transparency (https://certificate.transparency.dev/) · Let's Encrypt — Docs (https://letsencrypt.org/docs/) · Mozilla — Server Side TLS (https://wiki.mozilla.org/Security/Server_Side_TLS)

HSTS — enforce encryption in the browser

Unverified · Severity: OK · Not scored

Couldn't be checked — no usable HTTPS response was obtained. Not scored.

No response with headers was received, so this header wasn't evaluated and is excluded from the score.

Source data: Response headers from https://hsbc.com/
No HTTPS response received
$ curl -sIL https://hsbc.com/
Documentation: MDN — Strict-Transport-Security (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Strict-Transport-Security) · RFC 6797 — HSTS (https://www.rfc-editor.org/rfc/rfc6797) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

CSP — protection from script injection

Unverified · Severity: OK · Not scored

Couldn't be checked — no usable HTTPS response was obtained. Not scored.

No response with headers was received, so this header wasn't evaluated and is excluded from the score.

Source data: Response headers from https://hsbc.com/
No HTTPS response received
$ curl -sIL https://hsbc.com/
Documentation: MDN — Content Security Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP) · OWASP — CSP Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/Content_Security_Policy_Cheat_Sheet.html)

Clickjacking protection

Unverified · Severity: OK · Not scored

Couldn't be checked — no usable HTTPS response was obtained. Not scored.

No response with headers was received, so this header wasn't evaluated and is excluded from the score.

Source data: Response headers from https://hsbc.com/
No HTTPS response received
$ curl -sIL https://hsbc.com/
Documentation: MDN — X-Frame-Options (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Frame-Options) · OWASP — Clickjacking Defense (https://cheatsheetseries.owasp.org/cheatsheets/Clickjacking_Defense_Cheat_Sheet.html)

X-Content-Type-Options

Unverified · Severity: OK · Not scored

Couldn't be checked — no usable HTTPS response was obtained. Not scored.

No response with headers was received, so this header wasn't evaluated and is excluded from the score.

Source data: Response headers from https://hsbc.com/
No HTTPS response received
$ curl -sIL https://hsbc.com/
Documentation: MDN — X-Content-Type-Options (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/X-Content-Type-Options) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

Referrer-Policy

Unverified · Severity: OK · Not scored

Couldn't be checked — no usable HTTPS response was obtained. Not scored.

No response with headers was received, so this header wasn't evaluated and is excluded from the score.

Source data: Response headers from https://hsbc.com/
No HTTPS response received
$ curl -sIL https://hsbc.com/
Documentation: MDN — Referrer-Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Referrer-Policy) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

Permissions-Policy

Unverified · Severity: OK · Not scored

Couldn't be checked — no usable HTTPS response was obtained. Not scored.

No response with headers was received, so this header wasn't evaluated and is excluded from the score.

Source data: Response headers from https://hsbc.com/
No HTTPS response received
$ curl -sIL https://hsbc.com/
Documentation: MDN — Permissions-Policy (https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Permissions-Policy) · OWASP — HTTP Headers Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html)

DNSSEC — signed DNS records

Needs attention · Severity: Medium · Hardening gap · 0/7

The domain's records aren't signed, so in some scenarios users could be redirected to a forged server.

No DS record is published at the parent zone, so there's no DNSSEC chain of trust for this zone.

Source data: DNS-over-HTTPS (Cloudflare / Google): AD flag and DS record at the parent
AD = false
DS hsbc.com: NODATA
$ dig +short DS hsbc.com
Fix recommendation (effort: Medium)
  1. Enable DNSSEC at your DNS provider (one click at most providers).
  2. Copy the DS record your provider generates to your domain registrar.
  3. Wait for propagation and verify with DNSViz.
dig +dnssec hsbc.com SOA
delv hsbc.com

Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. A wrong DS record at the registrar will make the domain stop resolving — copy it exactly from the provider.

Documentation: RFC 4033 — DNSSEC (https://www.rfc-editor.org/rfc/rfc4033) · ICANN — DNSSEC: what and why (https://www.icann.org/resources/pages/dnssec-what-is-it-why-important-2019-03-05-en)

CAA — who may issue certificates

Needs attention · Severity: Low · Hardening gap · 0/5

Any certificate authority can issue a certificate for the domain, raising the risk of mis-issuance.

No CAA records found. RFC 8659 lets the domain owner restrict which CAs are authorized.

Source data: DNS CAA hsbc.com
(no CAA records found)
$ dig +short CAA hsbc.com
Fix recommendation (effort: Easy)
  1. Identify which certificate authority issued your current certificate (see the certificate check).
  2. Publish CAA for that authority only, and add iodef to receive alerts.
hsbc.com.  CAA  0 issue "letsencrypt.org"
hsbc.com.  CAA  0 iodef "mailto:security@hsbc.com"

Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. If your CDN issues certificates on your behalf, include it too — otherwise certificate renewal will fail.

Documentation: RFC 8659 — CAA (https://www.rfc-editor.org/rfc/rfc8659)

DNS server redundancy

Passed · Severity: OK · 3/3

The domain is served by several DNS servers, so one server failing won't take it down.

6 NS servers.

Source data: DNS NS hsbc.com
ns20.hsbc.net
ns6.hsbc.com
ns20.hsbc.uk
ns21.hsbc.uk
ns21.hsbc.net
ns3.hsbc.com
$ dig +short NS hsbc.com
Documentation: RFC 2182 — Secondary DNS server operation (https://www.rfc-editor.org/rfc/rfc2182)

Indicative alignment

Best-practice mapping of public findings to common frameworks. Passive scanning tests public configuration only; it doesn't prove compliance or a violation.

  • Google & Yahoo sender rulesNo gaps observed
  • PCI DSS v4.01 observed gaps · 5 unverified
  • NIS2 / vendor due diligence2 observed gaps · 3 unverified
  • SOC 2 / ISO 27001 baseline6 unverified

Indicative alignment only, based on public configuration. It doesn't establish whether a framework applies to you, and it isn't legal advice, an audit or a certification.

Public DNS records

Ahsbc.com91.214.6.62 | 193.108.75.62
AAAAhsbc.com—
MXhsbc.com10 mxb-00299f02.gslb.pphosted.com | 10 mxa-00299f02.gslb.pphosted.com
NShsbc.comns20.hsbc.net | ns6.hsbc.com | ns20.hsbc.uk | ns21.hsbc.uk | ns21.hsbc.net | ns3.hsbc.com
TXThsbc.com6F33-A96D-4A70-B2F3-8980-0DA9-C687-9C2F | 5700a0f161c3ee56b1cdb45f8ff0d606 | f9fe8b945d159604d4fe56f68fd5a851 | 7c573538-4895-4bd2-90b9-13ecb67623b3 | mongodb-site-verification=IZGVt2wuFTz4U2KdEQTxNjbTM5MQ4agI | _github-challenge-hsbc-ent.hsbc.com=2c0124c517 | docker-verification=2885f98d-883c-4171-88f5-44ebc35fd452 | pendo-domain-verification=680c814a-0ddf-4099-8055-d7cc73af8d5a | docusign=dd1edf13-79d6-4d57-ae88-ba915685297c | docker-verification=0a84016e-f30a-49a9-8a41-ef819b497664 | docusign=e04d54f1-8d92-40bb-a780-2409999953c1 | oMhmK373syyyImHpn7IVEXhqDzNC | wiz-domain-verification=63f5e2e7316847f581f5c811d2057ac4c60fcff9e35a208a5cc63dda5808334f | atlassian-domain-verification=MVrygCbxi4sy2tdpLKAsoHvnI7n6c7A07JAYd14laoh1RGylTMluWtKlGkVbBHoR | JcqN2r7Z4NJrQpM4OGXTOw | wiz-domain-verification=c4f9ca2f3b5e74b4502b2756d19f0936af847728b0927c6bf47b5271b5331bd1 | wiz-domain-verification=0287380846b97f4f0f2a4ff03e53728406f0dce9a75011a27fed7b4df9f4027f | jamf-site-verification=hUHjpDIEEf1eN5Q7FhUbZw | work-accounts-domain-verification=p5eoAgBQd4EsOnDg2LKRdQ3g3rPYty | v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com include:spf-00299f02.pphosted.com include:spf1.hsbc.com include:spf2.hsbc.com include:spf3.hsbc.com include:spf-002f0603.pphosted.com ~all | google-site-verification=NI7zII4Ge_p28m0XfsDGMj77Nly4XabBi4MonUEVcUM | google-site-verification=vPkZv7fjzUVwP2apQBxXmbtPQb0PAhU5k9KuxnAwr5o | google-site-verification=M4iN_PX9kRTMMWq44Gj5N0yCKw21840zwBXdoBk1XJM | adobe-idp-site-verification=97bd1b56bb7c1bf2b021fcc1aa99f303be57821beda2e03442612fe631a071e5 | webexdomainverification.=de5860e7-75ed-4687-9345-095d6298d12b | webexdomainverification.=e10dece0-359f-4aa8-85f9-8fd61121b3c1 | webexdomainverification.JO59=608c80a0-fcc1-4022-8b7f-d99cee31b523 | webexdomainverification.GVLY=f509eddc-026a-40ff-896d-94a2a7c5089a | webexdomainverification.L2W7=69ac8949-902f-4c8c-90d0-4a0d3dcedb1c | webexdomainverification.L2W2=72eed45f-93c2-4f58-8c1f-407b22083b6c | webexdomainverification.=cf1ab7f9-8d4c-4d37-aff4-4a88b437614c | 96b06eef013a4fa7ba21975d52f6cea8ba5586141e604aad968e8e8a6a6b0d0c | adobe-sign-verification=33807990c7278c58bea18223c41dcf38 | c77e0dfe9d1771b49cbbf615650b24e | 8219-5848-B517-278B-A270-122C-5E8F-C5ED
TXT_dmarc.hsbc.comv=DMARC1; p=reject; fo=1; ri=3600; rua=mailto:dmarc_rua@emaildefense.proofpoint.com; ruf=mailto:dmarc_ruf@emaildefense.proofpoint.com
CAAhsbc.com—
DShsbc.com—
Passive check only: reading public DNS records, Certificate Transparency logs and ordinary GET requests to the homepage over HTTPS and HTTP. No changes were made to the scanned domain. Results are an indication and do not replace a professional security assessment.

Check your own domain