billdorr.com security report

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

64risk

Elevated

Several issues worth triaging this week.

0Critical

2High

3Medium

4Low

2Info

Collected 19 hours ago15.1sfrom cache

Certificate Transparency15
DNS resolution15
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs8
Registration
DNS posture2
Email authentication1
Certificate
Security headers0
Archived URLs
Analysis11

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.

A visitor who types the address without https, or follows an old link, gets the unencrypted site. On public Wi-Fi that page can be read and rewritten in transit.
What to do
Redirect every http:// request to https:// with a 301, then add HSTS.
asset: https://billdorr.com/
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.billdorr.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@billdorr.com"`, review the reports, then move to p=quarantine and p=reject.
asset: billdorr.com
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://billdorr.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://billdorr.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://billdorr.com/
104.225.208.26 (billdorr.com) reports openresty 1.31.1.1, lua-nginx-module 1.31.1.1, exim 4.99.5. 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: 104.225.208.26
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://billdorr.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://billdorr.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: billdorr.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: billdorr.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: billdorr.com

final https://billdorr.com/status 200time 1500msstack cloudflare

✗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

✓Receives mail via 1 server
billdorr.com
!SPFends in ~all
v=spf1 ip4:104.225.208.26 ip4:107.190.132.98 +a +mx +ip4:184.171.251.130 ~all
✗DMARC
no record
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓2 nameservers
ns107.nixihost.com ns108.nixihost.com

✓Registered with GoDaddy.com, LLC20.5 years old
billdorr.com
✓Registration expiry541 days
2028-03-01
✓Transfer lock
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
✓2 nameservers at registry
ns107.nixihost.com ns108.nixihost.com

Address	Ports	CVEs	Edge	Network
104.225.208.26 billdorr.com +18	5380110443587208320862087	0	direct	—

Archived URLs

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

billdorr.com security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames