suomienglantisanakirja.fi security report

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

82risk

Critical

Exposed services or known CVEs need attention now.

1Critical

1High

5Medium

5Low

2Info

Collected 4 hours ago6.8sfrom cache

Domain—

unavailable

Certificate Transparency
DNS resolution1
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs5
Registration
DNS posture2
Email authentication1
Certificate
Security headers0
Archived URLs
Analysis14

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.
noteRegistration did not complete (HTTP 406). Results below are partial.

Shodan matched these CVEs against the service banners it saw on 95.170.82.163 (suomienglantisanakirja.fi), which advertise nginx 1.1.19, openssh 5.9p1, php 5.3.10. 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-2024-25117 CVE-2024-3566 CVE-2022-31629 CVE-2022-31628 CVE-2022-4900 CVE-2021-23017 CVE-2021-3618 CVE-2020-11579 CVE-2019-20372 CVE-2019-9641 CVE-2019-9639 CVE-2019-9638 CVE-2019-9637 CVE-2019-9024 CVE-2019-9023 ...and 235 more
What to do
Confirm the running versions on 95.170.82.163 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2024-25117 ↗CVE-2024-3566 ↗CVE-2022-31629 ↗CVE-2022-31628 ↗CVE-2022-4900 ↗
asset: 95.170.82.163
SPF and DKIM alone do not protect the From: address a person sees. Without DMARC, a spoofed message can pass SPF for some other domain and still display yours.
What to do
Publish `_dmarc.suomienglantisanakirja.fi TXT "v=DMARC1; p=none; rua=mailto:dmarc@suomienglantisanakirja.fi"`, review the reports, then move to p=quarantine and p=reject.
asset: suomienglantisanakirja.fi
95.170.82.163 (suomienglantisanakirja.fi) reports nginx 1.1.19, openssh 5.9p1, php 5.3.10. 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.170.82.163
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.170.82.163: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://www.suomienglantisanakirja.fi/
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.suomienglantisanakirja.fi/
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.suomienglantisanakirja.fi/
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 95.170.82.163: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://www.suomienglantisanakirja.fi/
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.suomienglantisanakirja.fi/
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.suomienglantisanakirja.fi/
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: suomienglantisanakirja.fi
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: suomienglantisanakirja.fi
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: suomienglantisanakirja.fi

final https://www.suomienglantisanakirja.fi/status 200time 2909msstack cloudflare · PHP/5.3.10-1ubuntu3.15

✓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
mx3.mail.ovh.net mx4.mail.ovh.net
!SPFends in ~all
v=spf1 include:mx.ovh.com ~all
✗DMARC
no record
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓2 nameservers
dns12.ovh.net ns12.ovh.net

Address	Ports	CVEs	Edge	Network
95.170.82.163 suomienglantisanakirja.fi +2	2225804438649	250	direct	—

Archived URLs

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

suomienglantisanakirja.fi security report

Critical

Findings

Security headers

Email authentication

DNS

Hosts

Hostnames