laakarilehti.fi security report

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

88risk

Critical

Exposed services or known CVEs need attention now.

2Critical

0High

9Medium

8Low

2Info

Collected 14 hours ago28.7sfrom cache

Domain—

unavailable

Certificate Transparency13
DNS resolution13
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs12
Registration
DNS posture4
Email authentication2
Certificate
Security headers2
Archived URLs
Analysis21

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 94.237.35.151 (stat.laakarilehti.fi), which advertise http server 2.4.52, openssh 8.9p1. 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-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 CVE-2026-33007 ...and 61 more
What to do
Confirm the running versions on 94.237.35.151 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-49975 ↗CVE-2026-44631 ↗CVE-2026-44186 ↗CVE-2026-44185 ↗CVE-2026-44119 ↗
asset: 94.237.35.151
Shodan matched these CVEs against the service banners it saw on 83.143.222.9 (aristotesti.laakarilehti.fi), which advertise http server 2.4.52. 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-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 CVE-2026-33007 ...and 61 more
What to do
Confirm the running versions on 83.143.222.9 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-49975 ↗CVE-2026-44631 ↗CVE-2026-44186 ↗CVE-2026-44185 ↗CVE-2026-44119 ↗
asset: 83.143.222.9
94.237.35.151 (stat.laakarilehti.fi) reports http server 2.4.52, openssh 8.9p1. 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: 94.237.35.151
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: 94.237.35.151:22
83.143.222.9 (aristotesti.laakarilehti.fi) reports http server 2.4.52. 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: 83.143.222.9
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.laakarilehti.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.laakarilehti.fi/
The browser will also send this cookie over plain http://, where it can be captured.
What to do
Add `Secure` to the cookie.
asset: https://www.laakarilehti.fi/
The browser will also send this cookie over plain http://, where it can be captured.
What to do
Add `Secure` to the cookie.
asset: https://www.laakarilehti.fi/
The browser will also send this cookie over plain http://, where it can be captured.
What to do
Add `Secure` to the cookie.
asset: https://www.laakarilehti.fi/
Receivers are asked to report spoofing but not to block it. This is the right first step, and the wrong place to stop.
What to do
Once reports look clean, move to p=quarantine, then p=reject.
asset: laakarilehti.fi
34.88.18.194 (uutiskirje.laakarilehti.fi) reports varnish cache 7.1. 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: 34.88.18.194
Check it is not an open relay.
What to do
Restrict 25/tcp to a VPN, bastion, or allow-listed source range.
asset: 34.88.18.194:25
stage.laakarilehti.fi 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.laakarilehti.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.laakarilehti.fi/
Without HttpOnly, any injected script can read and exfiltrate this cookie.
What to do
Add `HttpOnly` unless client-side code genuinely needs to read it.
asset: https://www.laakarilehti.fi/
Without HttpOnly, any injected script can read and exfiltrate this cookie.
What to do
Add `HttpOnly` unless client-side code genuinely needs to read it.
asset: https://www.laakarilehti.fi/
Without HttpOnly, any injected script can read and exfiltrate this cookie.
What to do
Add `HttpOnly` unless client-side code genuinely needs to read it.
asset: https://www.laakarilehti.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: laakarilehti.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: laakarilehti.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: laakarilehti.fi

final https://www.laakarilehti.fi/status 200time 2077msstack cloudflare

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

✓Cookie wires
Secure · HttpOnly · SameSite=lax
✗Cookie _pk_ses.1.66e6
no Secure · no HttpOnly · no SameSite
✗Cookie _pk_id.1.66e6
no Secure · no HttpOnly · no SameSite
✗Cookie _pk_cvar.1.66e6
no Secure · no HttpOnly · no SameSite

✓Receives mail via 1 server
laakarilehti-fi.mail.protection.outlook.com
✓SPFends in -all
v=spf1 include:_spf.mailersend.net ip4:193.64.206.1/24 ip4:83.143.221.96/29 ip4:212.68.13.131 ip4:212.68.13.132 ip4:83.143.222.0/28 include:servers.mcsv.net include:spf.lianamailer.com include:spf.protection.outlook.com ip4:83.143.222.6 -all
!DMARCp=none
v=DMARC1; p=none; aspf=r; adkim=r; pct=100; rua=mailto:rua-dmarc@laakariliitto.fi; ruf=mailto:ruf-dmarc@laakariliitto.fi;
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
–IPv6 (AAAA)IPv4 only
✓4 nameservers
ns1-33.azure-dns.com ns2-33.azure-dns.net ns3-33.azure-dns.org ns4-33.azure-dns.info

Address	Ports	CVEs	Edge	Network
94.237.35.151 stat.laakarilehti.fi +2	2280443	76	direct	—
34.88.18.194 uutiskirje.laakarilehti.fi +5	2580443	0	direct	—
83.143.222.7 laakarilehti.fi +7	80443	0	direct	—
83.143.222.9 aristotesti.laakarilehti.fi +2	80443	76	direct	—
35.228.228.4 betyopaikat.laakarilehti.fi +1	3307	0	direct	—
83.143.222.8 tyopaikat.laakarilehti.fi +1	80	0	direct	—
83.143.222.2 stage.laakarilehti.fi +4	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.

laakarilehti.fi security report

Critical

Findings

Security headers

Email authentication

DNS

Hosts

Hostnames