botland.com.pl security report

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

29risk

Moderate

Some surface to tighten, nothing urgent.

0Critical

0High

2Medium

5Low

2Info

Collected 21 hours ago71.9sfrom cache

Certificate Transparency25
DNS resolution23
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs51
Registration
DNS posture2
Email authentication2
Certificate
Security headers6
Archived URLs
Analysis9

noteFound 25 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.
note3 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

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: 157.53.227.1:22
Without clientTransferProhibited, a compromised registrar account can move the domain to another registrar in days, with no second step.
What to do
Enable the transfer lock (and registrar lock, if offered) in the registrar control panel.
asset: botland.com.pl
panel-test.botland.com.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: panel-test.botland.com.pl
old.botland.com.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: old.botland.com.pl
Browsers and the preload list expect at least six months; shorter values give little protection between visits.
What to do
Raise max-age to 31536000 (one year).
asset: https://botland.com.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: botland.com.pl
Not urgent, but worth confirming auto-renew is on and the card on file is current.
What to do
Check auto-renew.
asset: botland.com.pl
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: botland.com.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: botland.com.pl

final https://botland.com.pl/status 200time 1138msstack cloudflare

–http:// redirects to https://port 80 did not answer
!Strict-Transport-Security
max-age=2592000
✓Content-Security-Policy
frame-ancestors 'self' https://botland.cz https://botland.de https://botland.store;
✓Clickjacking protection
SAMEORIGIN
✓X-Content-Type-Options
nosniff
✓Referrer-Policy
strict-origin-when-cross-origin
✓Permissions-Policy
camera=(), microphone=(), accelerometer=(), gyroscope=(), magnetometer=(), usb=(), bluetooth=(), hid=(), serial=(), midi
–security.txt publishedoptional — tells researchers where to report bugs

✓Receives mail via 5 servers
alt1.aspmx.l.google.com alt2.aspmx.l.google.com alt3.aspmx.l.google.com alt4.aspmx.l.google.com+1
✓SPFends in -all
v=spf1 include:_spf.google.com include:_spf.jupiter.salesmanago.pl include:_spf.emaillabs.net.pl -all
✓DMARCp=reject
v=DMARC1; p=reject; sp=reject; rua=mailto:2ad1e0dc88344b6e8f73ffec13d5f09e@dmarc-reports.cloudflare.net
!MTA-STSinbound mail can be downgraded to plaintext

!DNSSECanswers can be forged
–CAAany CA may issue
✓IPv6 (AAAA)
✓2 nameservers
lucy.ns.cloudflare.com reese.ns.cloudflare.com

✓Registered with Thecamels Sp. z o.o.15.8 years old
botland.com.pl
!Registration expiry70 days
2026-11-15
✗Transfer lock
none
✓2 nameservers at registry
lucy.ns.cloudflare.com reese.ns.cloudflare.com

Address	Ports	Edge	Network
104.26.13.6 botland.com.pl +5	80443205320822083208620878080+2	Cloudflare~	—
172.67.75.139 botland.com.pl +6	80443205320822083208620878080+2	Cloudflare~	—
104.26.12.6 botland.com.pl +5	80443208220832086208780808443+1	Cloudflare~	—
143.244.50.82 cdn1.botland.com.pl +4	80443193533374321	direct	—
143.244.49.179 cdn2.botland.com.pl +4	80443193533374321	direct	—
138.199.9.104 cdn3.botland.com.pl +4	80443193533374321	direct	—
157.53.227.1 lp.botland.com.pl +4	2280443	direct	—
182.161.73.131 nqozgp.botland.com.pl	80443	direct	—
185.49.13.170 click.botland.com.pl +1	80443	direct	—
10.20.0.185 bpm.botland.com.pl +1	none known	direct	—

Archived URLs

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

botland.com.pl security report

Moderate

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames