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

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

How is hkex.com.hk's C security grade calculated?

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

How many subdomains does hkex.com.hk expose?

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

Public security report

hkex.com.hk security rating

70/100

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

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

Re-scan hkex.com.hk now

What this scan found

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

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

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

14 issue(s) need attention (1 high, 2 medium, 11 low), while 13 checks passed.

Infrastructure observed: mail is hosted by microsoft, DNS is served by akamai, traffic is fronted by akamai.

92 subdomain(s) of hkex.com.hk resolve publicly.

Score by category

Area	Score	Grade	Issues
DNS hygiene	84	B	2
email spoofing defences (SPF/DKIM/DMARC)	52	F	2
external attack surface	100	A	0
IP threat intelligence	—	—	0
reputation and credential exposure	100	A	0
TLS encryption and certificates	66	D	2
HTTP security headers	14	F	8

Issues found (14)

highSPF authorizes huge IP ranges (ip4:40.92.0.0/15, ip4:52.100.0.0/15)

Very large ranges (ip4:40.92.0.0/15, ip4:52.100.0.0/15) let anyone inside them - for example any customer of the same cloud provider - send mail as you.

1 asset(s) affected · worth +9 points · check an SPF record with the free SPF tool →

mediumCertificate chain is incomplete

Desktop browsers often fill the gap, but mobile apps, APIs and some browsers fail outright - so it works in your tests and breaks for real users.

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

mediumHSTS not enabled

Without it, an attacker can strip SSL on the first HTTP request and keep the user on plaintext (SSL stripping), a common attack on public Wi-Fi.

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

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.

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

lowNo Content Security Policy

Without it, any injected script runs: session theft, fake payment forms, or card-skimming scripts on compromised pages. CSP limits the damage even when something else fails.

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

lowX-Content-Type-Options missing

Without it a file uploaded as an image can be executed as HTML/JavaScript on your domain, stealing same-site cookies and sessions.

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

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 →

lowCookies without Secure/HttpOnly (___Host-)

Missing Secure lets cookies travel in plaintext; missing HttpOnly lets injected scripts steal sessions; missing SameSite enables CSRF. Affected: ___Host-.

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

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 →

lowContent Security Policy is weak (no script-src/default-src; object-src not restricted)

The policy is too permissive (no script-src/default-src; object-src not restricted), so injected scripts still run while giving a false sense of security.

1 asset(s) affected · worth +1 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.

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

lowHSTS max-age is only 0 days

At 0 days the protection expires between visits, periodically reopening the window for SSL stripping.

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

lowNo clickjacking protection

Without it, attackers overlay a transparent frame of your page and trick users into clicking real actions such as transfers or password changes (clickjacking).

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

Checks passed

Mail exchangers configured
DMARC policy is enforced
DKIM signing keys found
Name servers are redundant
HSTS enabled
Clickjacking protection enabled
MIME sniffing disabled
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: microsoft
dns provider: akamai
cdn: akamai
subdomain count: 92

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.
Website not reachable 3 host(s)
The site could not be fetched, so its response headers and page content were not checked.
No Referrer-Policy 4 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
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 3 host(s)
The page returned HTTP 400 (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.
HTTPS not available on port 443 3 host(s)
The TLS checks could not run on this host, so its TLS configuration was not verified.

Frequently asked questions about hkex.com.hk security

Does hkex.com.hk have DMARC protection against email spoofing?: Yes. hkex.com.hk publishes a DMARC record with p=reject at 100% coverage, so receiving providers should reject mail forged from @hkex.com.hk.
How is hkex.com.hk's C security grade calculated?: CyberTrust scores hkex.com.hk passively across 6 area(s) — external attack surface 100/100; reputation and credential exposure 100/100; DNS hygiene 84/100; TLS encryption and certificates 66/100; email spoofing defences (SPF/DKIM/DMARC) 52/100; HTTP security headers 14/100 — and combines them by weight into the overall score of 70/100, which maps to grade C.
What is the most serious issue found on hkex.com.hk?: SPF authorizes huge IP ranges (ip4:40.92.0.0/15, ip4:52.100.0.0/15) (severity high). Very large ranges (ip4:40.92.0.0/15, ip4:52.100.0.0/15) let anyone inside them - for example any customer of the same cloud provider - send mail as you. Fixing it is worth about +9 points.
How many subdomains does hkex.com.hk expose?: This scan observed 92 publicly resolvable subdomain(s) for hkex.com.hk. Verified owners get the full list, with each host's open ports and running services.

What a verified owner of hkex.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 hkex.com.hk (free) → Open the live interactive report →