fortum.pl security report

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

66risk

Elevated

Several issues worth triaging this week.

1Critical

0High

2Medium

21Low

1Info

Collected 8 hours ago7.8sfrom cache

Domain—

unavailable

Certificate Transparency268
DNS resolution17
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs14
Registration
DNS posture4
Email authentication2
Certificate
Security headers5
Archived URLs
Analysis25

noteFound 268 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.
noteRegistration 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.

Shodan matched these CVEs against the service banners it saw on 151.101.194.137 (www.fortum.pl), which advertise http server 2.4.68. 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-2013-4365 CVE-2013-2765 CVE-2013-0942 CVE-2013-0941 CVE-2012-4360 CVE-2012-4001 CVE-2012-3526 CVE-2011-2688 CVE-2011-1176 CVE-2009-2299 CVE-2009-0796 CVE-2007-4723
What to do
Confirm the running versions on 151.101.194.137 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2013-4365 ↗CVE-2013-2765 ↗CVE-2013-0942 ↗CVE-2013-0941 ↗CVE-2012-4360 ↗
asset: 151.101.194.137
151.101.194.137 (www.fortum.pl) reports http server 2.4.68. 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: 151.101.194.137
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.fortum.pl/
admin.fortum.pl 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.fortum.pl
dev.fortum.pl 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: dev.fortum.pl
staging.fortum.pl 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: staging.fortum.pl
aio-test.fortum.pl 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: aio-test.fortum.pl
blog.dev.fortum.pl 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: blog.dev.fortum.pl
qa-online.fortum.pl 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: qa-online.fortum.pl
qa.cieplo.fortum.pl 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: qa.cieplo.fortum.pl
beta.media.fortum.pl 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: beta.media.fortum.pl
sklep-test.fortum.pl 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: sklep-test.fortum.pl
zapisy.dev.fortum.pl 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: zapisy.dev.fortum.pl
dcs-dev.aws.fortum.pl 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: dcs-dev.aws.fortum.pl
portal-test.fortum.pl 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: portal-test.fortum.pl
test-online.fortum.pl 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: test-online.fortum.pl
test.cieplo.fortum.pl 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: test.cieplo.fortum.pl
beta.forkast.fortum.pl 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: beta.forkast.fortum.pl
dcs-test.aws.fortum.pl 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: dcs-test.aws.fortum.pl
hcdl-dev.aws.fortum.pl 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: hcdl-dev.aws.fortum.pl
optimum.beta.fortum.pl 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: optimum.beta.fortum.pl
www.blog.dev.fortum.pl 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: www.blog.dev.fortum.pl
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.fortum.pl/
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: fortum.pl
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: fortum.pl

final https://www.fortum.pl/status 200time 1381msstack cloudflare

–http:// redirects to https://port 80 did not answer
✓Strict-Transport-Security
max-age=31557600; includeSubDomains
✓Content-Security-Policy
upgrade-insecure-requests; default-src https: data: 'unsafe-inline' 'unsafe-eval'; frame-ancestors 'self' *.wdr.io *.fortum.com *.fortum.se *.fortum.no *.fortum…
✓Clickjacking protection
SAMEORIGIN
✓X-Content-Type-Options
nosniff
✓Referrer-Policy
no-referrer, strict-origin-when-cross-origin
–Permissions-Policyoptional
–security.txt publishedoptional — tells researchers where to report bugs

✗Cookie country
no Secure · no HttpOnly · no SameSite

✓Receives mail via 1 server
fortum-pl.mail.protection.outlook.com
✓SPFends in -all
v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email include:spf.protection.outlook.com -all
✓DMARCp=reject
v=DMARC1; p=reject; rua=mailto:dmarc_agg@vali.email,mailto:dmarc_reporting@fortum.com; ruf=mailto:dmarc_reporting@fortum.com; fo=1
✓MTA-STSinbound mail must use TLS

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

Address	Ports	CVEs	Edge	Network
4.245.3.129 aio-test.fortum.pl +1	80443	0	direct	—
199.36.158.100 fortum.pl +3	80443	0	direct	—
151.101.2.137 www.fortum.pl +10	80443	0	direct	—
151.101.66.137 www.fortum.pl +4	80443	0	direct	—
151.101.130.137 www.fortum.pl +4	80443	0	direct	—
151.101.194.137 www.fortum.pl +5	80443	12	direct	—
4.210.211.41 sklep-test.fortum.pl +1	80443	0	direct	—
10.129.190.183 dcs-test.aws.fortum.pl	none known	0	direct	—
10.129.190.36 dcs-test.aws.fortum.pl	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.

fortum.pl security report

Elevated

Findings

Security headers

Email authentication

DNS

Hosts

Hostnames