bradtguides.com security report

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

35risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

0High

3Medium

4Low

2Info

Collected 18 hours ago14.7sfrom cache

Certificate Transparency8
DNS resolution10
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs29
Registration
DNS posture2
Email authentication2
Certificate
Security headers4
Archived URLs
Analysis9

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.

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: 5.75.162.223:22
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.bradtguides.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: bradtguides.com
5.75.162.223 (staging.bradtguides.com) reports openssh 8.2p1. 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: 5.75.162.223
81.130.169.13 (rdg.bradtguides.com) reports internet information services 10.0. 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: 81.130.169.13
staging.bradtguides.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: staging.bradtguides.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: bradtguides.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: bradtguides.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: bradtguides.com

final https://www.bradtguides.com/status 200time 1573msstack cloudflare · WordPress 7.0.4

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

✓Receives mail via 1 server
bradtguides-com.mail.protection.outlook.com
✓SPFends in -all
v=spf1 include:spf.protection.outlook.com include:spf.sendinblue.com mx -all
!DMARCp=none
v=DMARC1; p=none; sp=none; rua=mailto:dmarc@mailinblue.com!10m; ruf=mailto:dmarc@mailinblue.com!10m; rf=afrf; pct=100; ri=86400
!MTA-STSinbound mail can be downgraded to plaintext

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

✓Registered with 123-Reg Limited23.8 years old
bradtguides.com
✓Registration expiry433 days
2027-11-14
✓Transfer lock
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
✓2 nameservers at registry
venkat.ns.cloudflare.com virginia.ns.cloudflare.com

Address	Ports	Edge	Network
172.67.153.1 www.bradtguides.com +4	80443205220532082208320862087+5	Cloudflare~	—
104.21.49.225 www.bradtguides.com +5	80443205220532082208320862087+5	Cloudflare~	—
5.75.162.223 staging.bradtguides.com +1	22443	direct	—
81.130.169.13 rdg.bradtguides.com +2	443	direct	—

Archived URLs

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

bradtguides.com security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames