e-adz.net security report

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

50risk

Elevated

Several issues worth triaging this week.

0Critical

1High

3Medium

3Low

2Info

Collected 9 hours ago3.9sfrom cache

Certificate Transparency3
DNS resolution2
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs0
Registration
DNS posture2
Email authentication1
Certificate
Security headers0
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.

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.e-adz.net TXT "v=DMARC1; p=none; rua=mailto:dmarc@e-adz.net"`, review the reports, then move to p=quarantine and p=reject.
asset: e-adz.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://e-adz.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://e-adz.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: https://e-adz.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://e-adz.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: https://e-adz.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: e-adz.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: e-adz.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: e-adz.net

final https://e-adz.net/status 200time 1678msstack 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.e-adz.net
!SPFends in ~all
v=spf1 a mx ip4:23.153.104.141 ip4:23.153.104.141 ~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
ns10.e-adz.net ns9.e-adz.net

✓Registered with OnlineNIC, Inc.20.6 years old
e-adz.net
✓Registration expiry162 days
2027-02-16
✓Transfer lock
client delete prohibited, client transfer prohibited
✓2 nameservers at registry
ns10.e-adz.net ns9.e-adz.net

Address	Ports	CVEs	Edge	Network
23.153.104.141 e-adz.net +1	none known	0	direct	—

Archived URLs

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

e-adz.net security report

Elevated

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames