haema.de security report

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

81risk

Critical

Exposed services or known CVEs need attention now.

0Critical

4High

9Medium

15Low

2Info

Collected 12 hours ago16.0sfrom cache

Certificate Transparency50
DNS resolution18
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs35
Registration
DNS posture3
Email authentication2
Certificate
Security headers1
Archived URLs
Analysis30

noteFound 50 hostnames; this runtime allows 50 outbound requests per scan, so the 21 most likely to matter were resolved.
noteFound 16 addresses; enriching the first 12.
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 185.207.228.184 (www.haema.de), which advertise openssh 7.4rn, php 8.3.33. 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-2013-2220 CVE-2007-3205
What to do
Confirm the running versions on 185.207.228.184 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2013-2220 ↗CVE-2007-3205 ↗
asset: 185.207.228.184
Database engines should sit behind a private network.
What to do
Restrict 3306/tcp to a VPN, bastion, or allow-listed source range.
asset: 195.201.3.115:3306
Database engines should sit behind a private network.
What to do
Restrict 5432/tcp to a VPN, bastion, or allow-listed source range.
asset: 195.201.3.115:5432
Shodan matched these CVEs against the service banners it saw on 62.157.220.246 (ftp.haema.de), which advertise nginx 1.18.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-2025-23419 CVE-2023-44487 CVE-2021-23017 CVE-2021-3618
What to do
Confirm the running versions on 62.157.220.246 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2025-23419 ↗CVE-2023-44487 ↗CVE-2021-23017 ↗CVE-2021-3618 ↗
asset: 62.157.220.246
185.207.228.184 (www.haema.de) reports openssh 7.4rn, php 8.3.33. 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: 185.207.228.184
FTP transmits credentials in cleartext.
What to do
Restrict 21/tcp to a VPN, bastion, or allow-listed source range.
asset: 185.207.228.184:21
FTP transmits credentials in cleartext.
What to do
Restrict 21/tcp to a VPN, bastion, or allow-listed source range.
asset: 195.201.3.115:21
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: 195.201.3.115:22
62.157.220.246 (ftp.haema.de) reports nginx 1.18.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: 62.157.220.246
FTP transmits credentials in cleartext.
What to do
Restrict 21/tcp to a VPN, bastion, or allow-listed source range.
asset: 62.157.220.246: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://www.haema.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.haema.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://www.haema.de/
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 185.207.228.184:25
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 159.92.152.14:25
vpn.haema.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: vpn.haema.de
aw-vpn.haema.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: aw-vpn.haema.de
www.vpn.haema.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: www.vpn.haema.de
www.aw-vpn.haema.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: www.aw-vpn.haema.de
preview.haema.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: preview.haema.de
staging.haema.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: staging.haema.de
qa.termine.haema.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: qa.termine.haema.de
www.staging.haema.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: www.staging.haema.de
qa.termineapp.haema.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: qa.termineapp.haema.de
www.qa.termine.haema.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: www.qa.termine.haema.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.haema.de/
Exact versions in response headers let anyone match the server against a CVE feed without touching it.
What to do
Strip version tokens (`ServerTokens Prod`, `server_tokens off`, remove X-Powered-By).
asset: https://www.haema.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: haema.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: haema.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: haema.de

final https://www.haema.de/status 200time 1372msstack cloudflare · PHP/8.3.33 · TYPO3 CMS

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

✓Receives mail via 1 server
haema-de.mail.protection.outlook.com
✓SPFends in -all
v=spf1 ptr include:spf.protection.outlook.com include:spf.crsend.com include:_spf.salesforce.com include:haema-de-spf-a.haema.de -all
✓DMARCp=reject
v=DMARC1; p=reject; pct=100; rua=mailto:dmarc_agg@vali.email; ruf=mailto:ruf-dmarc@grifols.com; fo=1
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓3 nameservers
ns1.domaindiscount24.net ns2.domaindiscount24.net ns3.domaindiscount24.net

Address	Ports	CVEs	Edge	Network
185.207.228.184 www.haema.de +2	212580110143443587993+4	2	direct	—
195.201.3.115 preview.haema.de +2	2122801434439939953306+1	0	direct	—
62.157.220.246 ftp.haema.de +1	2180443	4	direct	—
20.105.216.15 qa.termine.haema.de +3	80443	0	direct	—
159.92.145.229 view.mail.haema.de +1	80443	0	direct	—
159.92.137.238 click.mail.haema.de +2	80443	0	direct	—
159.92.129.249 cloud.mail.haema.de +2	80443	0	direct	—
5.22.145.16 staging.haema.de +2	80	0	direct	—
5.22.145.121 staging.haema.de +2	80	0	direct	—
159.92.152.14 mail.haema.de +6	25	0	direct	—
80.157.184.116 vpn.haema.de	none known	0	direct	—
62.157.220.245 smtp.haema.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.

haema.de security report

Critical

Findings

Security headers

Email authentication

DNS

Hosts

Hostnames