80078.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 55 minutes ago6.7sfrom cache

Certificate Transparency0
DNS resolution1
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs1
Registration
DNS posture2
Email authentication0
Certificate
Security headers2
Archived URLs
Analysis8

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

final https://80078.net/status 521time 305msstack 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
✓2 nameservers
f1g1ns1.dnspod.net f1g1ns2.dnspod.net

✓Registered with eName Technology Co., Ltd.16.3 years old
80078.net
✓Registration expiry246 days
2027-05-11
✓Transfer lock
client delete prohibited, client transfer prohibited
✓2 nameservers at registry
f1g1ns1.dnspod.net f1g1ns2.dnspod.net

Address	Ports	CVEs	Edge	Network
180.163.28.105 80078.net +1	80	0	direct	—

Archived URLs

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

80078.net security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames