paxio.net security report

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

62risk

Elevated

Several issues worth triaging this week.

0Critical

2High

3Medium

2Low

1Info

Collected 19 hours ago3.6sfrom cache

Certificate Transparency
DNS resolution4
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs8
Registration
DNS posture3
Email authentication0
Certificate
Security headers2
Archived URLs
Analysis8

noteCertificate Transparency did not complete (HTTP 404). 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.

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://paxio.net/
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.paxio.net TXT "v=DMARC1; p=none; rua=mailto:dmarc@paxio.net"`, review the reports, then move to p=quarantine and p=reject.
asset: paxio.net
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://paxio.net/
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://paxio.net/
Nothing tells receiving mail servers which hosts may send as @paxio.net, 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: paxio.net
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://paxio.net/
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: paxio.net
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: paxio.net

final https://paxio.net/status 526time 1297msstack cloudflare

✗http:// redirects to https://
✗Strict-Transport-Security
✗Content-Security-Policy
✓Clickjacking protection
SAMEORIGIN
✗X-Content-Type-Options
✓Referrer-Policy
same-origin
–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.paxio.net ns2.paxio.net ns3.paxio.net

✓Registered with GoDaddy.com, LLC23.4 years old
paxio.net
✓Registration expiry585 days
2028-04-13
✓Transfer lock
client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
✓3 nameservers at registry
ns1.paxio.net ns2.paxio.net ns3.paxio.net

Address	Ports	Edge	Network
96.45.83.246 paxio.net +2	80443	direct	—
96.45.83.30 paxio.net +3	80443	direct	—
96.45.82.130 paxio.net +1	80443	direct	—
96.45.82.77 paxio.net +3	80443	direct	—

Archived URLs

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

paxio.net security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames