pfalzkom.de security report

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

79risk

Critical

Exposed services or known CVEs need attention now.

1Critical

0High

6Medium

12Low

2Info

Collected 13 hours ago30.2sfrom cache

Certificate Transparency33
DNS resolution13
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs33
Registration
DNS posture2
Email authentication2
Certificate
Security headers0
Archived URLs
Analysis21

noteFound 33 hostnames; this runtime allows 50 outbound requests per scan, so the 21 most likely to matter were resolved.
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.

Shodan matched these CVEs against the service banners it saw on 95.179.165.55 (pfalzkom.de), which advertise exim 4.99.5, php 5.6.40, openssh 8.0. These are version-fingerprint matches, not confirmed exploits: a distribution may have back-ported the fix while leaving the banner unchanged. Severity reflects the volume of known issues associated with this host, not a CVSS score. CVE-2026-60002 CVE-2026-60001 CVE-2026-60000 CVE-2026-59999 CVE-2026-59998 CVE-2026-59997 CVE-2026-59996 CVE-2026-59995 CVE-2026-35414 CVE-2026-35388 CVE-2026-35387 CVE-2026-35385 CVE-2025-32728 CVE-2025-26465 CVE-2024-25117 ...and 29 more
What to do
Confirm the running versions on 95.179.165.55 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-60002 ↗CVE-2026-60001 ↗CVE-2026-60000 ↗CVE-2026-59999 ↗CVE-2026-59998 ↗
asset: 95.179.165.55
95.179.165.55 (pfalzkom.de) reports exim 4.99.5, php 5.6.40, openssh 8.0. 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: 95.179.165.55
FTP transmits credentials in cleartext.
What to do
Restrict 21/tcp to a VPN, bastion, or allow-listed source range.
asset: 212.65.4.52:21
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://pfalzkom.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://pfalzkom.de/
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://pfalzkom.de/
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: pfalzkom.de
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 95.179.165.55:25
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 212.65.4.52:25
dev-hp.pfalzkom.de appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: dev-hp.pfalzkom.de
dev-crm.pfalzkom.de appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: dev-crm.pfalzkom.de
dev-inside.pfalzkom.de appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: dev-inside.pfalzkom.de
dev-intranet.pfalzkom.de appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: dev-intranet.pfalzkom.de
dev-inside-api.pfalzkom.de appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: dev-inside-api.pfalzkom.de
dev-authentification.pfalzkom.de appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: dev-authentification.pfalzkom.de
dev-openinformer-api.pfalzkom.de appears in Certificate Transparency logs. Names like this usually front staging, admin, or internal tooling, which tends to be patched later and monitored less than production.
What to do
Confirm this host is meant to be public. If not, put it behind SSO or an allow-list.
asset: dev-openinformer-api.pfalzkom.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://pfalzkom.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://pfalzkom.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: pfalzkom.de
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: pfalzkom.de
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: pfalzkom.de

final https://pfalzkom.de/status 200time 1451msstack cloudflare · WPML ver:4.9.7 stt:1,3;

✓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 4 servers
mx01.hornetsecurity.com mx02.hornetsecurity.com mx03.hornetsecurity.com mx04.hornetsecurity.com
✓SPFends in -all
v=spf1 mx ip4:212.65.4.41 ip4:212.65.4.43 ip4:88.99.54.82 ip4:88.99.53.208 ip4:213.183.65.32 ip4:212.65.6.100 ip4:212.65.6.101 ip4:212.65.9.192/26 ip4:212.65.25.205 ip4:212.65.0.188 ip4:212.65.4.52 ip4:213.183.84.38 ip4:213.183.77.39 ip4:52.240.4.14 ip4:3.127.120.6 include:_spf.senders.scnem.com include:spf.hornetsecurity.com include:_spf.createsend.com -all
!DMARCp=none
v=DMARC1; p=none;
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓2 nameservers
dns.pfalzkom.de dns1.pfalzkom.de

Address	Ports	CVEs	Edge	Network
95.179.165.55 pfalzkom.de +17	255380110443465587993+9	44	direct	—
212.65.4.52 plesk.pfalzkom.de +2	212580110443465993995+1	0	direct	—
80.190.129.133 news.pfalzkom.de +2	80443	0	direct	—
35.157.18.158 matomo.pfalzkom.de +2	80443	0	direct	—
213.183.85.141 uc.pfalzkom.de	443	0	direct	—
213.206.177.140 mdm.pfalzkom.de +2	443	0	direct	—
212.65.0.150 inside.pfalzkom.de +1	443	0	direct	—
213.206.190.20 dev-hp.pfalzkom.de +1	none known	0	direct	—
213.206.185.210 did.pfalzkom.de	none known	0	direct	—
212.65.25.206 adfs.pfalzkom.de	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.

pfalzkom.de security report

Critical

Findings

Security headers

Email authentication

DNS

Hosts

Hostnames