softarchive.net security report

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

60risk

Elevated

Several issues worth triaging this week.

0Critical

2High

2Medium

4Low

2Info

Collected 16 hours ago6.6sfrom cache

Certificate Transparency
DNS resolution1
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs6
Registration
DNS posture2
Email authentication1
Certificate
Security headers0
Archived URLs
Analysis10

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

The site could not be loaded over HTTPS and answered only at http://ww1.softarchive.net/. Every visit — including any login or form — travels unencrypted and can be read or rewritten by anyone on the path. Browsers mark the page "Not secure".
What to do
Get a certificate (Let’s Encrypt is free), serve the site on 443, then redirect port 80 to it and add HSTS.
asset: http://ww1.softarchive.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.softarchive.net TXT "v=DMARC1; p=none; rua=mailto:dmarc@softarchive.net"`, review the reports, then move to p=quarantine and p=reject.
asset: softarchive.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: http://ww1.softarchive.net/
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: http://ww1.softarchive.net/
64.31.3.237 (softarchive.net) reports openssh 8.9p1. 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: 64.31.3.237
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: http://ww1.softarchive.net/
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: http://ww1.softarchive.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: softarchive.net
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: softarchive.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: softarchive.net

final http://ww1.softarchive.net/status 200time 2754msstack 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
mail.h-email.net
✓SPFends in -all
v=spf1 ip6:fd9c:d030:168c::/48 -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
ns1.brainydns.com ns2.brainydns.com

✓Registered with Dynadot Inc21.8 years old
softarchive.net
✓Registration expiry798 days
2028-11-12
✓Transfer lock
client transfer prohibited
✓2 nameservers at registry
ns1.brainydns.com ns2.brainydns.com

Address	Ports	CVEs	Edge	Network
64.31.3.237 softarchive.net +2	5380443102280808444	0	direct	—

Archived URLs

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

softarchive.net security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames