Does hsbc.com.hk have DMARC protection against email spoofing?

Yes. hsbc.com.hk publishes a DMARC record with p=reject at 100% coverage, so receiving providers should reject mail forged from @hsbc.com.hk.

How is hsbc.com.hk's B security grade calculated?

CyberTrust scores hsbc.com.hk passively across 6 area(s) — external attack surface 100/100; reputation and credential exposure 100/100; TLS encryption and certificates 90/100; email spoofing defences (SPF/DKIM/DMARC) 84/100; DNS hygiene 84/100; HTTP security headers 74/100 — and combines them by weight into the overall score of 89/100, which maps to grade B.

How many subdomains does hsbc.com.hk expose?

This scan observed 186 publicly resolvable subdomain(s) for hsbc.com.hk. Verified owners get the full list, with each host's open ports and running services.

Public security report

hsbc.com.hk security rating

89/100

A means lowest risk and F means highest, like a school report card. How the score is calculated →

Scanned 2026-10-30 · 7 issue(s) found · 14 checks passed

Re-scan hsbc.com.hk now

What this scan found

CyberTrust assessed hsbc.com.hk passively — using only information that is publicly visible on the internet: DNS records, certificates, response headers and reachable services. The result is 89/100, grade B, where A means lowest risk and F means highest, like a school report card.

Email spoofing is blocked: hsbc.com.hk publishes a DMARC record with p=reject at 100% coverage, so mail forged from @hsbc.com.hk should be rejected by major providers.

Strongest area: external attack surface (100/100). Weakest area: HTTP security headers (74/100).

7 issue(s) need attention (7 low), while 14 checks passed.

Infrastructure observed: mail is hosted by proofpoint, traffic is fronted by cloudfront, the web server identifies as apache.

186 subdomain(s) of hsbc.com.hk resolve publicly.

Score by category

Area	Score	Grade	Issues
DNS hygiene	84	B	2
email spoofing defences (SPF/DKIM/DMARC)	84	B	2
external attack surface	100	A	0
IP threat intelligence	—	—	0
reputation and credential exposure	100	A	0
TLS encryption and certificates	90	A	1
HTTP security headers	74	C	2

Issues found (7)

lowContent Security Policy is weak (script-src 'unsafe-inline'; script-src 'unsafe-eval')

The policy is too permissive (script-src 'unsafe-inline'; script-src 'unsafe-eval'), so injected scripts still run while giving a false sense of security.

5 asset(s) affected · worth +2 points · how to set HSTS, CSP and other security headers →

lowHSTS preload not enabled

Even with HSTS on, the very first visit is still exposed to SSL-stripping: the header only takes effect after one successful HTTPS visit. Browsers ship a preload list (Chromium's list is used by Chrome, Edge, Safari and Firefox) so the first connection goes straight to HTTPS.

2 asset(s) affected · worth +2 points · how to set HSTS, CSP and other security headers →

lowNo DKIM key found on common selectors

Without DKIM, mail integrity cannot be verified and DMARC loses one of its two authentication pillars. Note we probed only 46 common selectors, so a custom selector may exist.

1 asset(s) affected · worth +2 points · look up DKIM keys with the free DKIM tool →

lowNo MTA-STS policy

Without it an attacker on the network path can force a downgrade to plaintext and read or modify mail such as contracts and payment details.

1 asset(s) affected · worth +2 points · how to stop email spoofing with SPF, DKIM and DMARC →

lowNo OCSP stapling

The server does not staple the certificate revocation status. Every revocation check becomes an extra round trip to the CA, which slows the first visit and, if the CA endpoint is unreachable or the visitor's network blocks it, leaves the browser without a usable revocation status.

2 asset(s) affected · worth +1 points · check a certificate with the free SSL tool →

lowNo CAA record

Without it any CA may issue certificates for your domain, enabling a lookalike site with a valid padlock.

1 asset(s) affected · worth +1 points · see who can issue certificates with the free CAA tool →

lowDNSSEC not enabled

Without it, attackers can poison caches or forge answers and send visitors to a lookalike server that harvests credentials.

1 asset(s) affected · worth +1 points · what DNSSEC prevents and how to enable it →

Checks passed

Mail exchangers configured
SPF record is valid
DMARC policy is enforced
Name servers are redundant
HSTS enabled
Clickjacking protection enabled
MIME sniffing disabled
No API keys found in front-end bundles
Only modern TLS versions are enabled
No weak cipher suites accepted
Certificate is valid and trusted
No risky services found exposed
No shadow-AI services exposed
No mail-server IP on spam blocklists

What we detected

mail provider: proofpoint
cdn: cloudfront
web server: apache
subdomain count: 186

What could not be fully checked

No BIMI record
BIMI shows your logo next to authenticated mail in supporting inboxes (requires an enforcing DMARC policy). It is a trust signal rather than a security control, so it does not affect your score.
No TLS-RPT record
TLS-RPT sends you reports when other servers fail to deliver mail to you securely. Recommended alongside MTA-STS.
No Referrer-Policy 3 host(s)
Browsers default to strict-origin-when-cross-origin today; setting it explicitly is good hygiene.
No Permissions-Policy 4 host(s)
Permissions-Policy disables powerful browser features (camera, microphone, geolocation) you do not use.
No security.txt 2 host(s)
security.txt (RFC 9116) tells security researchers how to report vulnerabilities to you instead of posting them publicly.
Website returned an error page — partly unassessed 5 host(s)
The page returned HTTP 403 (often a firewall challenge for automated clients), so most header and content checks could not run. HSTS was still assessed where the response is reliable, but this category is only partially evaluated and its score should be read as incomplete.

Frequently asked questions about hsbc.com.hk security

Does hsbc.com.hk have DMARC protection against email spoofing?: Yes. hsbc.com.hk publishes a DMARC record with p=reject at 100% coverage, so receiving providers should reject mail forged from @hsbc.com.hk.
How is hsbc.com.hk's B security grade calculated?: CyberTrust scores hsbc.com.hk passively across 6 area(s) — external attack surface 100/100; reputation and credential exposure 100/100; TLS encryption and certificates 90/100; email spoofing defences (SPF/DKIM/DMARC) 84/100; DNS hygiene 84/100; HTTP security headers 74/100 — and combines them by weight into the overall score of 89/100, which maps to grade B.
What is the most serious issue found on hsbc.com.hk?: Content Security Policy is weak (script-src 'unsafe-inline'; script-src 'unsafe-eval') (severity low). The policy is too permissive (script-src 'unsafe-inline'; script-src 'unsafe-eval'), so injected scripts still run while giving a false sense of security. Fixing it is worth about +2 points.
How many subdomains does hsbc.com.hk expose?: This scan observed 186 publicly resolvable subdomain(s) for hsbc.com.hk. Verified owners get the full list, with each host's open ports and running services.

What a verified owner of hsbc.com.hk sees

Everything above is what anyone can observe from the internet. Domain owners who verify ownership additionally get the full asset inventory — every subdomain with its open ports and running services — look-alike and typosquatting domains registered against the brand, credential-exposure monitoring, and copy-paste fixes for each finding.

Verify ownership of hsbc.com.hk (free) → Open the live interactive report →