theex.com security report

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

39risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

0High

3Medium

7Low

2Info

Collected 3 hours ago14.1sfrom cache

Certificate Transparency11
DNS resolution20
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs73
Registration
DNS posture4
Email authentication2
Certificate
Security headers0
Archived URLs
Analysis12

noteFound 14 addresses; enriching the first 12.
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.
note4 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

Without HSTS the browser will still try http:// first on a fresh visit, which is the window an on-path attacker uses.
What to do
Send `Strict-Transport-Security: max-age=31536000; includeSubDomains` once you are sure everything works over HTTPS.
asset: https://www.theex.com/
CSP is the main defence that limits what an injected script can do. Without it, any XSS bug is fully exploitable.
What to do
Start with a report-only policy, tighten it against the reports, then enforce.
asset: https://www.theex.com/
No X-Frame-Options or CSP frame-ancestors directive, so another site can load this page invisibly inside its own and trick users into clicking.
What to do
Send `X-Frame-Options: DENY` or `Content-Security-Policy: frame-ancestors ’none’`.
asset: https://www.theex.com/
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 40.99.9.82:25
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 40.99.10.98:25
vpn.theex.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.theex.com
www.vpn.theex.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: www.vpn.theex.com
Lets browsers guess content types, which turns some upload and text endpoints into script injection points.
What to do
Send `X-Content-Type-Options: nosniff` on every response.
asset: https://www.theex.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.theex.com/
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: theex.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: theex.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: theex.com

final https://www.theex.com/status 200time 364msstack cloudflare · WP Engine

✓http:// redirects to https://
✗Strict-Transport-Security
✗Content-Security-Policy
✗Clickjacking protection
✗X-Content-Type-Options
✗Referrer-Policy
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✓Cookie __cf_bm
Secure · HttpOnly · SameSite=none

✓Receives mail via 1 server
theex-com.mail.protection.outlook.com
✓SPFends in -all
v=spf1 a mx ip4:206.223.181.9 ip4:206.223.181.33 ip4:206.223.181.42 ip4:72.2.50.6 a:mail.explace.on.ca include:spf.mandrillapp.com include:mailgun.org include:spf.protection.outlook.com -all
✓DMARCp=quarantine
v=DMARC1; p=quarantine
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓4 nameservers
ns1-33.azure-dns.com ns2-33.azure-dns.net ns3-33.azure-dns.org ns4-33.azure-dns.info

✓Registered with GoDaddy.com, LLC30.3 years old
theex.com
✓Registration expiry258 days
2027-05-24
✓Transfer lock
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
✓4 nameservers at registry
ns1-33.azure-dns.com ns2-33.azure-dns.net ns3-33.azure-dns.org ns4-33.azure-dns.info

Address	Ports	Edge	Network
141.193.213.20 theex.com +5	80443205220532082208320862087+5	Cloudflare~	—
141.193.213.21 theex.com +6	80443205220532082208320862087+5	Cloudflare~	—
141.193.213.10 vendorpartnerportal.theex.com +3	80443205220532082208320862087+5	Cloudflare~	—
141.193.213.11 vendorpartnerportal.theex.com +3	80443205220532082208320862087+5	Cloudflare~	—
40.99.9.82 mail.theex.com +14	2580110143443587993995	direct	—
40.99.10.98 mail.theex.com +14	2580110443587993995	direct	—
206.223.181.127 vpn.theex.com +2	80443	direct	—
40.99.9.88 autodiscover.theex.com	80	direct	—
40.104.210.8 autodiscover.theex.com	80	direct	—
52.98.50.24 autodiscover.theex.com	80	direct	—
40.99.9.120 autodiscover.theex.com	80	direct	—
169.55.131.40 cms.theex.com	none known	direct	—

Archived URLs

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

theex.com security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames