thingsyoudidntknow.com security report

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

56risk

Elevated

Several issues worth triaging this week.

0Critical

0High

7Medium

4Low

2Info

Collected 20 hours ago19.8sfrom cache

Certificate Transparency6
DNS resolution9
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs62
Registration
DNS posture4
Email authentication2
Certificate
Security headers0
Archived URLs
Analysis13

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.

FTP transmits credentials in cleartext.
What to do
Restrict 21/tcp to a VPN, bastion, or allow-listed source range.
asset: 165.140.254.191:21
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://thingsyoudidntknow.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://thingsyoudidntknow.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://thingsyoudidntknow.com/
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://thingsyoudidntknow.com/
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://thingsyoudidntknow.com/
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: thingsyoudidntknow.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://thingsyoudidntknow.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://thingsyoudidntknow.com/
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://thingsyoudidntknow.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: thingsyoudidntknow.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: thingsyoudidntknow.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: thingsyoudidntknow.com

final https://thingsyoudidntknow.com/status 200time 245msstack cloudflare · WordPress 7.0.4

✓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 ezfs_649546
no Secure · no HttpOnly · no SameSite
✗Cookie ezoictest
no Secure · HttpOnly · no SameSite

✓Receives mail via 1 server
thingsyoudidntknow-com.mail.protection.outlook.com
✓SPFends in -all
v=spf1 include:secureserver.net include:_spf.emailcampaigns.net -all
!DMARCp=none
v=DMARC1; p=none; rua=mailto:mail@thingsyoudidntknow.com; ruf=mailto:mail@thingsyoudidntknow.com; sp=none;
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
✓IPv6 (AAAA)
✓4 nameservers
havanese.ezoicns.com scorpion.ezoicns.com seahorse.ezoicns.com stingray.ezoicns.com

✓Registered with GoDaddy.com, LLC3.0 years old
thingsyoudidntknow.com
✓Registration expiry360 days
2027-09-01
✓Transfer lock
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
✓2 nameservers at registry
havanese.ezoicns.com scorpion.ezoicns.com

Address	Ports	Edge	Network
104.21.84.156 www.thingsyoudidntknow.com	80443205220532082208320862087+5	Cloudflare~	—
172.67.194.145 www.thingsyoudidntknow.com +2	80443205220532082208320862087+5	Cloudflare~	—
104.21.79.186 email.r2.thingsyoudidntknow.com +3	80443205220532082208320862087+5	Cloudflare~	—
172.67.147.25 email.r2.thingsyoudidntknow.com +4	80443205220532082208320862087+5	Cloudflare~	—
165.140.254.191 tracking.u.thingsyoudidntknow.com +1	2180110443587	direct	—
20.225.97.235 rs-stripe.thingsyoudidntknow.com +2	804438480	direct	—
52.221.42.138 thingsyoudidntknow.com +2	80443	direct	—

Archived URLs

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

thingsyoudidntknow.com security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames