https://faz.net
Analyse abgeschlossen. 8 Schwachstellen gefunden · Score 7/100.
Unlock 2 masked findings
2 e-mails · clean PDF report · history
Critical findings — act immediately
The following item should be fixed immediately:
-
Domain expires in 1 days
If the domain is not renewed in time, the entire site goes offline – including all e-mail addresses.
Sensitive reconnaissance findings
Recon · OSINT 🔒 maskedThis section contains sensitive findings (e-mails found, sensitive paths, server versions). For visitors without an account, actual values are masked — only count and status are shown. → Sign in for full view
pr●●●@●●●.de
ve●●●@●●●.de
🔒 2 e-mails readable by spam bots — sign up for free for the full list
Quick Wins — biggest impact
These 3 changes raise your score the most.
7 → 57
-
1
Domain expires in 1 days
+25 ⏱ 10 Minuten · leichtIf the domain is not renewed in time, the entire site goes offline – including all e-mail addresses.
-
2
No SPF record i SPF Sender Policy Framework: DNS record that defines which servers are allowed to send e-mail on behalf of your domain. The most important baseline protection against e-mail spoofing.
+15 ⏱ 10 Minuten · leichtAnyone can send e-mails on behalf of this domain.
-
3
WordPress: CVE-2024-6386 (High)
+10 ⏱ 30–60 Minuten · mittelAuthenticated Server-Side Template Injection in Elementor Plugin
+ 5 more vulnerabilities — see the list below
Scan categories
SSL & HTTPS
Passed ✓
HTTP headers
Issues ✗
DNS & infrastructure
Passed ✓
E-mail protection
Issues ✗
Open ports
Passed ✓
GDPR
Passed ✓
Vulnerabilities found
Domain expires in 1 days
If the domain is not renewed in time, the entire site goes offline – including all e-mail addresses.
+ 7 more vulnerabilities locked
Including action items & fixes — unlock for free
Save this report as PDF
With a free account: full PDF report with screenshot, Quick Wins, all recommendations and step-by-step fixes — perfect to show, archive or pass on to clients.
Terms in this report
Understand what we found — the key concepts behind the findings, briefly explained.
SSL & TLS
How SSL/TLS certificates work, how the handshake unfolds and what to watch for when checking — explained in plain English.
HSTS (Strict-Transport-Security) forces browsers permanently to HTTPS. Learn how the header is built, what includeSubDomains and p…
CAA records define which certificate authorities are allowed to issue SSL certificates for your domain. Protection against mis-iss…
DMARC protects your domain from e-mail spoofing. Learn how the record is structured, what p=none/quarantine/reject mean and how to…
SPF (Sender Policy Framework) prevents foreign servers from sending e-mails under your domain name. Structure, mechanisms and best…
DKIM signs your outgoing e-mails cryptographically — the recipient can reliably verify a mail came from you. Structure, selectors …
HTTP headers
The Content-Security-Policy is the most important browser-side defence against XSS. Learn how a CSP is structured and how to roll …
X-Frame-Options prevents clickjacking by controlling whether your site can be embedded in an iframe. Values DENY, SAMEORIGIN and t…
The Referrer-Policy controls which information is sent when users click external links. Values, privacy implications and safe defa…
The Permissions-Policy selectively disables browser features like geolocation, microphone, camera and FLoC. Structure, all directi…
X-Content-Type-Options: nosniff prevents browsers from guessing the MIME type of files. Protection against cross-site-scripting an…
Frontend & APIs
SRI protects external JavaScript and CSS files against tampering on the CDN. Hash-based integrity verification in the browser — ex…
Cross-Origin Resource Sharing controls which foreign sites may call your APIs. Same-Origin policy, preflight requests and the key …
Secure, HttpOnly and SameSite — the three most important cookie flags and what they do. How to harden sessions against XSS, MITM a…