kzawag.com security report

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

77risk

Critical

Exposed services or known CVEs need attention now.

1Critical

0High

6Medium

6Low

1Info

Collected 8 hours ago5.3sfrom cache

Certificate Transparency3
DNS resolution3
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs14
Registration
DNS posture1
Email authentication2
Certificate
Security headers0
Archived URLs
Analysis14

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.

Redis defaults to no authentication and allows writing files to disk.
What to do
Restrict 6379/tcp to a VPN, bastion, or allow-listed source range.
asset: 163.172.105.205:6379
Public SSH invites credential stuffing and key brute force.
What to do
Restrict 22/tcp to a VPN, bastion, or allow-listed source range.
asset: 163.172.105.205:22
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://kzawag.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://kzawag.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://kzawag.com/
The record ends in ?all, so a spoofed message is neither passed nor failed and most receivers let it through.
What to do
End the record with -all (or ~all while you validate your senders).
asset: kzawag.com
Receivers are asked to report spoofing but not to block it. This is the right first step, and the wrong place to stop.
What to do
Once reports look clean, move to p=quarantine, then p=reject.
asset: kzawag.com
163.172.105.205 (www.kzawag.com) 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: 163.172.105.205
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 163.172.105.205:25
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://kzawag.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://kzawag.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: kzawag.com
Not urgent, but worth confirming auto-renew is on and the card on file is current.
What to do
Check auto-renew.
asset: kzawag.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: kzawag.com

final https://kzawag.com/status 200time 969msstack 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

✓Cookie PHPSESSID
Secure · HttpOnly · SameSite=none

✓Receives mail via 1 server
mail.kzawag.com
!SPFends in ?all
v=spf1 a mx a:kzawag.com ip4:163.172.105.205 ip4:163.172.105.205 ip4:163.172.105.205 ip6:fe80::ec4:7aff:fe0e:99e8 ?all
!DMARCp=none
v=DMARC1; pct=100; ruf=mailto:postmaster@kzawag.com; rua=mailto:postmaster@zawag.org; p=none
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
✓CAA
0 issuewild "letsencrypt.org"
✓IPv6 (AAAA)
✓1 nameserver
dns1.zaoag.com

✓Registered with NameCheap, Inc.12.9 years old
kzawag.com
!Registration expiry51 days
2026-10-28
✓Transfer lock
client transfer prohibited
✓2 nameservers at registry
dns1.zaoag.com dns2.zaoag.com

Address	Ports	CVEs	Edge	Network
163.172.105.205 www.kzawag.com +6	22255380143443465587+6	0	direct	—

Archived URLs

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

kzawag.com security report

Critical

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames