trafford.com security report

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

75risk

Critical

Exposed services or known CVEs need attention now.

1Critical

1High

3Medium

3Low

2Info

Collected 8 hours ago12.2sfrom cache

Certificate Transparency14
DNS resolution18
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs33
Registration
DNS posture2
Email authentication2
Certificate
Security headers4
Archived URLs
Analysis10

noteFound 17 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.

Shodan matched these CVEs against the service banners it saw on 192.232.249.212 (m.trafford.com), which advertise exim 4.99.5, mysql 5.7.44-48, openssh 9.9. These are version-fingerprint matches, not confirmed exploits: a distribution may have back-ported the fix while leaving the banner unchanged. Severity reflects the volume of known issues associated with this host, not a CVSS score. CVE-2026-60002 CVE-2026-60001 CVE-2026-60000 CVE-2026-59999 CVE-2026-59998 CVE-2026-59997 CVE-2026-59996 CVE-2026-59995 CVE-2026-35414 CVE-2026-35388 CVE-2026-35387 CVE-2026-35385 CVE-2025-32728 CVE-2025-26466 CVE-2025-26465 ...and 3 more
What to do
Confirm the running versions on 192.232.249.212 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-60002 ↗CVE-2026-60001 ↗CVE-2026-60000 ↗CVE-2026-59999 ↗CVE-2026-59998 ↗
asset: 192.232.249.212
Database engines should sit behind a private network.
What to do
Restrict 3306/tcp to a VPN, bastion, or allow-listed source range.
asset: 192.232.249.212:3306
192.232.249.212 (m.trafford.com) reports exim 4.99.5, mysql 5.7.44-48, openssh 9.9. Publishing precise versions lets anyone match the host against a CVE feed without probing it, which is how targets get shortlisted for mass exploitation after a new advisory lands.
What to do
Suppress version tokens in server banners (for example `ServerTokens Prod` in Apache) and keep the packages current.
asset: 192.232.249.212
FTP transmits credentials in cleartext.
What to do
Restrict 21/tcp to a VPN, bastion, or allow-listed source range.
asset: 192.232.249.212:21
Receivers are asked to report spoofing but not to block it. This is the right first step, and the wrong place to stop.
What to do
Once reports look clean, move to p=quarantine, then p=reject.
asset: trafford.com
stage.trafford.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.trafford.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.trafford.com/en
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: trafford.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: trafford.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: trafford.com

final https://www.trafford.com/enstatus 200time 3699msstack cloudflare

✓http:// redirects to https://
✓Strict-Transport-Security
max-age=15768000
✓Content-Security-Policy
<options and value>
✓Clickjacking protection
SAMEORIGIN
✓X-Content-Type-Options
nosniff
✗Referrer-Policy
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✓Cookie shell#lang
Secure · HttpOnly · no SameSite
✓Cookie ASP.NET_SessionId
Secure · HttpOnly · no SameSite
✓Cookie SC_ANALYTICS_GLOBAL_COOKIE
Secure · HttpOnly · no SameSite
✓Cookie trafford#lang
Secure · HttpOnly · no SameSite

✓Receives mail via 2 servers
cluster5.us.messagelabs.com cluster5a.us.messagelabs.com
✓SPFends in -all
v=spf1 ip4:206.53.252.80 ip4:206.53.249.125 include:cust-spf.exacttarget.com include:_spf.salesforce.com include:spf.protection.outlook.com -all
!DMARCp=none
v=DMARC1; p=none; rua=mailto:dmarcsupport@authorsolutions.com; ruf=mailto:dmarcsupport@authorsolutions.com; fo=1:d:s; adkim=s; aspf=s
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓2 nameservers
ns1.authorsolutions.com ns2.authorsolutions.com

✓Registered with Network Solutions, LLC30.9 years old
trafford.com
✓Registration expiry414 days
2027-10-27
✓Transfer lock
client transfer prohibited
✓2 nameservers at registry
ns1.authorsolutions.com ns2.authorsolutions.com

Address	Ports	CVEs	Edge	Network
192.232.249.212 m.trafford.com +9	21265380110143443465+9	18	direct	—
206.53.245.180 www.trafford.com +1	80443	0	direct	—
13.111.210.129 click.mail.trafford.com	80443	0	direct	—
13.33.88.58 image.mail.trafford.com +2	80443	0	direct	—
13.33.88.7 image.mail.trafford.com +2	80443	0	direct	—
13.33.88.106 image.mail.trafford.com +2	80443	0	direct	—
13.33.88.100 image.mail.trafford.com +3	80443	0	direct	—
13.111.209.120 cloud.mail.trafford.com	80443	0	direct	—
13.111.212.136 view.mail.trafford.com	80443	0	direct	—
206.53.245.150 stage.trafford.com	none known	0	direct	—
68.66.208.181 blog.trafford.com	none known	0	direct	—
206.246.145.57 books.trafford.com	none known	0	direct	—

Archived URLs

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

trafford.com security report

Critical

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames