gruenebrise.de security report

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

69risk

Elevated

Several issues worth triaging this week.

1Critical

0High

4Medium

9Low

2Info

Collected 5 hours ago84.2sfrom cache

Headers—

unavailable

Certificate Transparency26
DNS resolution28
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs72
Registration
DNS posture3
Email authentication2
Certificate
Security headers
Archived URLs
Analysis16

noteFound 26 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.
noteSecurity headers did not complete (Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits). Results below are partial.
note4 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

Shodan matched these CVEs against the service banners it saw on 5.75.247.48 (stage.gruenebrise.de), which advertise http server 2.4.58. 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-49975 CVE-2026-48913 CVE-2026-44631 CVE-2026-44186 CVE-2026-44185 CVE-2026-44119 CVE-2026-43951 CVE-2026-42536 CVE-2026-42535 CVE-2026-34356 CVE-2026-34355 CVE-2026-34059 CVE-2026-34032 CVE-2026-33857 CVE-2026-33523 ...and 45 more
What to do
Confirm the running versions on 5.75.247.48 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-49975 ↗CVE-2026-48913 ↗CVE-2026-44631 ↗CVE-2026-44186 ↗CVE-2026-44185 ↗
asset: 5.75.247.48
FTP transmits credentials in cleartext.
What to do
Restrict 21/tcp to a VPN, bastion, or allow-listed source range.
asset: 193.53.247.78: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: 193.53.247.78:22
5.75.247.48 (stage.gruenebrise.de) reports http server 2.4.58. 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: 5.75.247.48
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.228.190:22
193.53.247.78 (069.gruenebrise.de) reports openssh 10.4. 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: 193.53.247.78
195.201.228.190 (old.gruenebrise.de) reports openssh 10.0p2. 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: 195.201.228.190
admin.gruenebrise.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: admin.gruenebrise.de
cdn.admin.gruenebrise.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: cdn.admin.gruenebrise.de
stage.gruenebrise.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: stage.gruenebrise.de
hza.stage.gruenebrise.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: hza.stage.gruenebrise.de
lba.stage.gruenebrise.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: lba.stage.gruenebrise.de
old.gruenebrise.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: old.gruenebrise.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: gruenebrise.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: gruenebrise.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: gruenebrise.de

✓Receives mail via 1 server
gruenebrise-de.mail.protection.outlook.com
✓SPFends in -all
v=spf1 include:27088937.spf06.hubspotemail.net include:spf.protection.outlook.com include:mail.zendesk.com -all
✓DMARCp=quarantine
v=DMARC1; p=quarantine; pct=100; rua=mailto:spoofing.report@gruenebrise.de; ruf=mailto:spoofing.report@gruenebrise.de; fo=1;
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
✓IPv6 (AAAA)
✓3 nameservers
ns.udag.de ns.udag.net ns.udag.org

Address	Ports	CVEs	Edge	Network
141.101.90.96 info.gruenebrise.de +5	80443205220532082208320862087+5	0	Cloudflare~	—
141.101.90.97 info.gruenebrise.de +5	80443205220532082208320862087+5	0	Cloudflare~	—
141.101.90.98 info.gruenebrise.de +4	80443205220532082208320862087+5	0	Cloudflare~	—
141.101.90.99 info.gruenebrise.de +4	80443205220532082208320862087+5	0	Cloudflare~	—
138.199.46.65 cdn.admin.gruenebrise.de +5	80443193533374321	0	direct	—
193.53.247.78 069.gruenebrise.de +4	212280443	0	direct	—
116.203.39.174 perf.gruenebrise.de +1	23796443910010250	0	direct	—
185.175.196.75 www.gruenebrise.de +7	80443	0	direct	—
5.75.247.48 stage.gruenebrise.de +2	80443	60	direct	—
51.158.210.82 admin.gruenebrise.de +3	80443	0	direct	—
195.201.228.190 old.gruenebrise.de +1	22	0	direct	—

Archived URLs

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

gruenebrise.de security report

Elevated

Findings

Email authentication

DNS

Hosts

Hostnames