wowperucken.de security report

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

56risk

Elevated

Several issues worth triaging this week.

0Critical

1High

4Medium

6Low

0Info

Collected 17 hours ago2.4sfrom cache

Certificate Transparency2
DNS resolution6
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs28
Registration
DNS posture2
Email authentication0
Certificate
Security headers2
Archived URLs
Analysis11

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.
noteNo registration data: RDAP has no record at this level.
note3 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

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.wowperucken.de TXT "v=DMARC1; p=none; rua=mailto:dmarc@wowperucken.de"`, review the reports, then move to p=quarantine and p=reject.
asset: wowperucken.de
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://www.wowperucken.de/
The browser will also send this cookie over plain http://, where it can be captured.
What to do
Add `Secure` to the cookie.
asset: https://www.wowperucken.de/
The browser will also send this cookie over plain http://, where it can be captured.
What to do
Add `Secure` to the cookie.
asset: https://www.wowperucken.de/
Nothing tells receiving mail servers which hosts may send as @wowperucken.de, 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: wowperucken.de
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://www.wowperucken.de/
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://www.wowperucken.de/
Without HttpOnly, any injected script can read and exfiltrate this cookie.
What to do
Add `HttpOnly` unless client-side code genuinely needs to read it.
asset: https://www.wowperucken.de/
Without HttpOnly, any injected script can read and exfiltrate this cookie.
What to do
Add `HttpOnly` unless client-side code genuinely needs to read it.
asset: https://www.wowperucken.de/
Without HttpOnly, any injected script can read and exfiltrate this cookie.
What to do
Add `HttpOnly` unless client-side code genuinely needs to read it.
asset: https://www.wowperucken.de/
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: wowperucken.de

final https://www.wowperucken.de/status 200time 934msstack cloudflare

✓http:// redirects to https://
✓Strict-Transport-Security
max-age=31536000
✗Content-Security-Policy
✓Clickjacking protection
SAMEORIGIN
✗X-Content-Type-Options
✗Referrer-Policy
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✗Cookie frontend
no Secure · no HttpOnly · no SameSite
!Cookie frontend_cid
Secure · no HttpOnly · no SameSite
✗Cookie landing_page
no Secure · no HttpOnly · no SameSite

–No MX records — domain does not receive mail
✗SPF
no record
✗DMARC
no record
–MTA-STSn/a

!DNSSECanswers can be forged
✓CAA
0 issue "comodoca.com" · 0 issue "digicert.com; cansignhttpexchanges=yes" · 0 issue "letsencrypt.org" · 0 issue "pki.goog; cansignhttpexchanges=yes" · 0 issue "ssl.com" · 0 issuewild "comodoca.com" · 0 issuewild "digicert.com; cansignhttpexchanges=yes" · 0 issuewild "letsencrypt.org" · 0 issuewild "pki.goog; cansignhttpexchanges=yes" · 0 issuewild "ssl.com"
✓IPv6 (AAAA)
✓2 nameservers
algin.ns.cloudflare.com beth.ns.cloudflare.com

Address	Ports	Edge	Network
172.67.71.142 wowperucken.de +2	80443208220832086208720968080+2	Cloudflare~	—
104.26.6.208 wowperucken.de +2	80443208220832086208780808443+1	Cloudflare~	—
104.26.7.208 wowperucken.de +2	80443208220832086208780808443+1	Cloudflare~	—

Archived URLs

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

wowperucken.de security report

Elevated

Findings

Security headers

Email authentication

DNS

Hosts

Hostnames