ello.ch security report

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

61risk

Elevated

Several issues worth triaging this week.

0Critical

1High

5Medium

4Low

2Info

Collected 2 hours ago6.8sfrom cache

Certificate Transparency
DNS resolution1
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs9
Registration
DNS posture4
Email authentication2
Certificate
Security headers0
Archived URLs
Analysis12

noteCertificate Transparency did not complete (HTTP 502). Results below are partial.
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.188.197.82 (ello.ch), which advertise openssh 9.2p1, exim 4.99.4. 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-66141 CVE-2026-66140
What to do
Confirm the running versions on 185.188.197.82 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-66141 ↗CVE-2026-66140 ↗
asset: 185.188.197.82
185.188.197.82 (ello.ch) reports openssh 9.2p1, exim 4.99.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: 185.188.197.82
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: 185.188.197.82: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://ello.ch/
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://ello.ch/
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://ello.ch/
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 185.188.197.82:25
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://ello.ch/
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://ello.ch/
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: ello.ch
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: ello.ch
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: ello.ch

final https://ello.ch/status 200time 645msstack cloudflare · Powered by WPBakery Page Builder - drag and drop page builder for WordPress.

✓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 1 server
ello-ch.mail.protection.outlook.com
✓SPFends in -all
v=spf1 include:spf.protection.outlook.com -all
✓DMARCp=reject
v=DMARC1; p=reject; rua=mailto:it@ello.ch; ruf=mailto:it@ello.ch; fo=1
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓4 nameservers
ns1.ello.ch ns2.ello.ch ns3.ello.ch ns4.ello.ch

Address	Ports	CVEs	Edge	Network
185.188.197.82 ello.ch +2	22255380443465587995+1	2	direct	—

Archived URLs

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

ello.ch security report

Elevated

Findings

Security headers

Email authentication

DNS

Hosts

Hostnames