bookishbeck.com security report

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

50risk

Elevated

Several issues worth triaging this week.

0Critical

1High

3Medium

3Low

1Info

Collected 21 hours ago13.2sfrom cache

Certificate Transparency
DNS resolution2
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs4
Registration
DNS posture3
Email authentication0
Certificate
Security headers1
Archived URLs
Analysis8

noteCertificate Transparency did not complete (HTTP 429). Results below are partial.
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.

SPF and DKIM alone do not protect the From: address a person sees. Without DMARC, a spoofed message can pass SPF for some other domain and still display yours.
What to do
Publish `_dmarc.bookishbeck.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@bookishbeck.com"`, review the reports, then move to p=quarantine and p=reject.
asset: bookishbeck.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://bookishbeck.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://bookishbeck.com/
Nothing tells receiving mail servers which hosts may send as @bookishbeck.com, so anyone can. Even a domain that sends no mail should say so, or it becomes a free spoofing target.
What to do
Publish `v=spf1 -all` to state that this domain sends no mail.
asset: bookishbeck.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://bookishbeck.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://bookishbeck.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: bookishbeck.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: bookishbeck.com

final https://bookishbeck.com/status 200time 31msstack cloudflare · WordPress.com

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

–No MX records — domain does not receive mail
✗SPF
no record
✗DMARC
no record
–MTA-STSn/a

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

✓Registered with Automattic Inc.3.4 years old
bookishbeck.com
✓Registration expiry224 days
2027-04-19
✓Transfer lock
client transfer prohibited
✓3 nameservers at registry
ns1.wordpress.com ns2.wordpress.com ns3.wordpress.com

Address	Ports	CVEs	Edge	Network
192.0.78.25 bookishbeck.com +45	80443	0	direct	—
192.0.78.24 bookishbeck.com +39	80443	0	direct	—

Archived URLs

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

bookishbeck.com security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames