eightcap.com security report

Certificate, security headers, email authentication, DNS, registration, and exposed hosts — from public sources.

30risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

0High

2Medium

23Low

2Info

Collected 6 hours ago36.1sfrom cache

Certificate Transparency181
DNS resolution3
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs4
Registration
DNS posture4
Email authentication2
Certificate
Security headers4
Archived URLs
Analysis27

noteFound 181 hostnames; this runtime allows 50 outbound requests per scan, so the 21 most likely to matter were resolved.
noteCertificate inspection is unavailable in this runtime.
noteNetwork ownership lookup is unavailable in this runtime; ASN and org are omitted.
noteCDN/WAF detection is unavailable in this runtime.

The browser will also send this cookie over plain http://, where it can be captured.
What to do
Add `Secure` to the cookie.
asset: https://www.eightcap.com/zh/traders/
The browser will also send this cookie over plain http://, where it can be captured.
What to do
Add `Secure` to the cookie.
asset: https://www.eightcap.com/zh/traders/
admin.eightcap.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: admin.eightcap.com
admin.blu.eightcap.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: admin.blu.eightcap.com
admin.dev.eightcap.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: admin.dev.eightcap.com
admin.eig.eightcap.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: admin.eig.eightcap.com
admin.fxs.eightcap.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: admin.fxs.eightcap.com
anz.admin.eightcap.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: anz.admin.eightcap.com
blu.admin.eightcap.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: blu.admin.eightcap.com
eig.admin.eightcap.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: eig.admin.eightcap.com
fcs.admin.eightcap.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: fcs.admin.eightcap.com
fns.admin.eightcap.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: fns.admin.eightcap.com
admin.stage.eightcap.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: admin.stage.eightcap.com
stage.admin.eightcap.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: stage.admin.eightcap.com
admin.eig.ops.eightcap.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: admin.eig.ops.eightcap.com
fns.admin.stage.eightcap.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: fns.admin.stage.eightcap.com
stage.eig.admin.eightcap.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: stage.eig.admin.eightcap.com
vpn.internal.eightcap.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: vpn.internal.eightcap.com
vpn-sydney.internal.eightcap.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: vpn-sydney.internal.eightcap.com
test-vpn-dummy.internal.eightcap.com appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: test-vpn-dummy.internal.eightcap.com
Full URLs — including any tokens or IDs in them — are sent to every third party the page links to.
What to do
Send `Referrer-Policy: strict-origin-when-cross-origin`.
asset: https://www.eightcap.com/zh/traders/
Without HttpOnly, any injected script can read and exfiltrate this cookie.
What to do
Add `HttpOnly` unless client-side code genuinely needs to read it.
asset: https://www.eightcap.com/zh/traders/
Without HttpOnly, any injected script can read and exfiltrate this cookie.
What to do
Add `HttpOnly` unless client-side code genuinely needs to read it.
asset: https://www.eightcap.com/zh/traders/
Without HttpOnly, any injected script can read and exfiltrate this cookie.
What to do
Add `HttpOnly` unless client-side code genuinely needs to read it.
asset: https://www.eightcap.com/zh/traders/
Answers for this domain are not signed, so a resolver cannot tell a forged response from a real one.
What to do
Enable DNSSEC at your DNS host and publish the DS record at the registrar.
asset: eightcap.com
Mail to this domain can be downgraded to plaintext by an on-path attacker, because senders have no way to know TLS is required.
What to do
Publish an MTA-STS policy (a TXT record plus a small HTTPS-hosted file).
asset: eightcap.com
Any public certificate authority may issue certificates for this domain. CAA lets you name the ones allowed to.
What to do
Add a CAA record naming your CA, e.g. `0 issue "letsencrypt.org"`.
asset: eightcap.com

final https://www.eightcap.com/zh/traders/status 200time 1648msstack cloudflare

✓http:// redirects to https://
✓Strict-Transport-Security
max-age=63072000
✓Content-Security-Policy
frame-ancestors 'none'; form-action 'self'
✓Clickjacking protection
DENY
✓X-Content-Type-Options
nosniff
✗Referrer-Policy
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

!Cookie 8cap-sitelang
Secure · no HttpOnly · SameSite=lax
✗Cookie cs-personalize-user-uid
no Secure · no HttpOnly · no SameSite
✗Cookie cs-personalize-manifest
no Secure · no HttpOnly · no SameSite

✓Receives mail via 7 servers
alt1.aspmx.l.google.com alt2.aspmx.l.google.com alt3.aspmx.l.google.com alt4.aspmx.l.google.com+3
!SPFends in ~all
v=spf1 include:_spf.google.com include:mail.zendesk.com include:spf.sendinblue.com include:_spf.salesforce.com include:amazonses.com include:spf.protection.outlook.com ~all
✓DMARCp=reject
v=DMARC1; p=reject; rua=mailto:ecn7ofvv@ag.au.dmarcian.com,mailto:dmarc-reports@eightcap.com;
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓4 nameservers
ns-1033.awsdns-01.org ns-1699.awsdns-20.co.uk ns-366.awsdns-45.com ns-887.awsdns-46.net

✓Registered with Amazon Registrar, Inc.15.5 years old
eightcap.com
✓Registration expiry171 days
2027-02-25
✓Transfer lock
client transfer prohibited
✓4 nameservers at registry
ns-1033.awsdns-01.org ns-1699.awsdns-20.co.uk ns-366.awsdns-45.com ns-887.awsdns-46.net

Address	Ports	CVEs	Edge	Network
64.239.109.1 eightcap.com +3	80443	0	direct	—
64.239.123.1 www.eightcap.com +3	80443	0	direct	—

Archived URLs

Endpoints the Wayback Machine has kept — config files, backups, scripts. Slow to fetch, so it is here on request.

eightcap.com security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames