treedom.net security report

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

65risk

Elevated

Several issues worth triaging this week.

1Critical

0High

2Medium

8Low

2Info

Collected 18 hours ago48.5sfrom cache

Headers—

unavailable

Domain—

unavailable

Certificate Transparency58
DNS resolution48
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs23
Registration
DNS posture4
Email authentication2
Certificate
Security headers
Archived URLs
Analysis13

noteFound 58 hostnames; this runtime allows 50 outbound requests per scan, so the 21 most likely to matter were resolved.
noteFound 34 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.
noteRegistration did not complete (Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits). Results below are partial.
noteSecurity headers did not complete (Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits). Results below are partial.

Shodan matched these CVEs against the service banners it saw on 188.245.251.112 (mautic-test.treedom.net), which advertise 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 188.245.251.112 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: 188.245.251.112
188.245.251.112 (mautic-test.treedom.net) reports 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: 188.245.251.112
Public SSH invites credential stuffing and key brute force.
What to do
Restrict 22/tcp to a VPN, bastion, or allow-listed source range.
asset: 188.245.251.112:22
beta.treedom.net 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: beta.treedom.net
test.treedom.net 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.treedom.net
stem.test.treedom.net 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: stem.test.treedom.net
assets.test.treedom.net 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: assets.test.treedom.net
mautic-test.treedom.net 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: mautic-test.treedom.net
medias.beta.treedom.net 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: medias.beta.treedom.net
footprint-calculator.test.treedom.net 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: footprint-calculator.test.treedom.net
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: treedom.net
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: treedom.net
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: treedom.net

✓Receives mail via 5 servers
alt1.aspmx.l.google.com alt2.aspmx.l.google.com alt3.aspmx.l.google.com alt4.aspmx.l.google.com+1
!SPFends in ~all
v=spf1 include:_spf.google.com include:sendgrid.net include:spf.customerly.io ~all
✓DMARCp=reject
v=DMARC1; p=reject; rua=mailto:mailmaster@treedom.net; ruf=mailto:mailmaster@treedom.net;
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓4 nameservers
ns-1079.awsdns-06.org ns-1718.awsdns-22.co.uk ns-43.awsdns-05.com ns-643.awsdns-16.net

Address	Ports	CVEs	Edge	Network
188.245.251.112 mautic-test.treedom.net +1	2280443644310250	18	direct	—
63.181.200.106 treedom.net +5	80443	0	direct	—
63.182.244.0 treedom.net +6	80443	0	direct	—
108.157.254.39 www.treedom.net +3	80443	0	direct	—
108.157.254.129 www.treedom.net +17	80443	0	direct	—
151.101.2.92 assets.test.treedom.net +72	80443	0	direct	—
151.101.66.92 assets.test.treedom.net +72	80443	0	direct	—
151.101.130.92 assets.test.treedom.net +1	80443	0	direct	—
151.101.194.92 assets.test.treedom.net +72	80443	0	direct	—
108.157.254.10 www.treedom.net +1	80	0	direct	—
108.157.254.43 www.treedom.net +1	80	0	direct	—
3.69.214.28 treedom.net +2	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.

treedom.net security report

Elevated

Findings

Email authentication

DNS

Hosts

Hostnames