bbwit.de security report

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

57risk

Elevated

Several issues worth triaging this week.

0Critical

0High

11Medium

8Low

1Info

Collected 17 hours ago36.3sfrom cache

Certificate Transparency30
DNS resolution19
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs39
Registration
DNS posture3
Email authentication2
Certificate
Security headers0
Archived URLs
Analysis20

noteFound 30 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.

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: 148.251.123.23:22
FTP transmits credentials in cleartext.
What to do
Restrict 21/tcp to a VPN, bastion, or allow-listed source range.
asset: 188.40.28.32: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: 188.40.28.32:22
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: 95.217.200.226:22
FTP transmits credentials in cleartext.
What to do
Restrict 21/tcp to a VPN, bastion, or allow-listed source range.
asset: 202.61.232.100: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: 202.61.232.100:22
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: 148.251.123.11:22
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://bbw-it.org/
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://bbw-it.org/
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://bbw-it.org/
The record ends in ?all, so a spoofed message is neither passed nor failed and most receivers let it through.
What to do
End the record with -all (or ~all while you validate your senders).
asset: bbwit.de
148.251.123.23 (nc.bbwit.de) reports bootstrap 3.4.1, 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: 148.251.123.23
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 188.40.28.32:25
95.217.200.226 (cmk.bbwit.de) reports bootstrap 3.4.1, 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: 95.217.200.226
202.61.232.100 (www.bbwit.de) reports openssh 8.4p1. 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: 202.61.232.100
148.251.123.11 (api.bbwit.de) reports openssh 9.2p1. 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: 148.251.123.11
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://bbw-it.org/
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://bbw-it.org/
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: bbwit.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: bbwit.de

final https://bbw-it.org/status 200time 4680msstack cloudflare · WordPress 7.1

✓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 2 servers
mail.bbwit.de.bbwit.de mxe866.netcup.net
!SPFends in ?all
v=spf1 mx ptr a:pmg.bbwit.de ip4:148.251.123.23 ?all
!DMARC
v=DMARC1; p= quarantine; rua=mailto:monitoring@bbwit.de; ruf=mailto:monitoring@bbwit.de; fo=0; adkim=r; aspf=r; pct=100; rf=afrf; ri=86400; sp=none
✓MTA-STSinbound mail must use TLS

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓3 nameservers
helium.ns.hetzner.de hydrogen.ns.hetzner.com oxygen.ns.hetzner.com

Address	Ports	Edge	Network
148.251.123.23 nc.bbwit.de +11	2280110143443465587993+7	direct	—
188.40.28.32 bbwit.de +5	21222580110143443465+3	direct	—
95.217.200.226 cmk.bbwit.de +4	2280443465993995	direct	—
202.61.232.100 www.bbwit.de +3	2122804438443	direct	—
148.251.123.11 api.bbwit.de +2	22443	direct	—

Archived URLs

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

bbwit.de security report

Elevated

Findings

Security headers

Email authentication

DNS

Hosts

Hostnames