hobbymaker.com security report

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

54risk

Elevated

Several issues worth triaging this week.

0Critical

0High

10Medium

11Low

2Info

Collected 17 hours ago24.3sfrom cache

Certificate Transparency28
DNS resolution14
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs22
Registration
DNS posture2
Email authentication2
Certificate
Security headers1
Archived URLs
Analysis23

noteFound 28 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.
note2 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

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.hobbymaker.com/en-gb/
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.hobbymaker.com/en-gb/
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.hobbymaker.com/en-gb/
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.hobbymaker.com/en-gb/
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.hobbymaker.com/en-gb/
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.hobbymaker.com/en-gb/
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.hobbymaker.com/en-gb/
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.hobbymaker.com/en-gb/
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.hobbymaker.com/en-gb/
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: hobbymaker.com
Browsers and the preload list expect at least six months; shorter values give little protection between visits.
What to do
Raise max-age to 31536000 (one year).
asset: https://www.hobbymaker.com/en-gb/
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.hobbymaker.com/en-gb/
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.hobbymaker.com/en-gb/
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.hobbymaker.com/en-gb/
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.hobbymaker.com/en-gb/
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.hobbymaker.com/en-gb/
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.hobbymaker.com/en-gb/
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.hobbymaker.com/en-gb/
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.hobbymaker.com/en-gb/
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.hobbymaker.com/en-gb/
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: hobbymaker.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: hobbymaker.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: hobbymaker.com

final https://www.hobbymaker.com/en-gb/status 200time 2059msstack cloudflare

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

✗Cookie userpreference
no Secure · no HttpOnly · SameSite=lax
✗Cookie userpreference
no Secure · no HttpOnly · SameSite=lax
✗Cookie userpreference
no Secure · no HttpOnly · SameSite=lax
✗Cookie userpreference
no Secure · no HttpOnly · SameSite=lax
✗Cookie userpreference
no Secure · no HttpOnly · SameSite=lax
✗Cookie userpreference
no Secure · no HttpOnly · SameSite=lax
✗Cookie userpreference
no Secure · no HttpOnly · SameSite=lax

✓Receives mail via 1 server
hobbymaker-com.mail.protection.outlook.com
✓SPFends in -all
v=spf1 include:spf.protection.outlook.com -all
!DMARCp=none
v=DMARC1; p=none;
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
✓IPv6 (AAAA)
✓2 nameservers
simon.ns.cloudflare.com val.ns.cloudflare.com

✓Registered with Gandi SAS27.6 years old
hobbymaker.com
✓Registration expiry144 days
2027-01-29
✓Transfer lock
client transfer prohibited
✓2 nameservers at registry
simon.ns.cloudflare.com val.ns.cloudflare.com

Address	Ports	CVEs	Edge	Network
172.66.166.207 www.hobbymaker.com +6	80443205220532082208320872095+4	0	Cloudflare~	—
104.20.31.85 www.hobbymaker.com +6	80443205320822083208620878080+2	0	Cloudflare~	—

Archived URLs

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

hobbymaker.com security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames