hosting-warszawa.com security report

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

91risk

Critical

Exposed services or known CVEs need attention now.

1Critical

4High

5Medium

2Low

2Info

Collected 12 hours ago8.4sfrom cache

Certificate Transparency0
DNS resolution1
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs16
Registration
DNS posture2
Email authentication0
Certificate
Security headers2
Archived URLs
Analysis14

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.

Shodan matched these CVEs against the service banners it saw on 193.105.125.170 (hosting-warszawa.com), which advertise exim 4.99.5, mariadb 10.6.19-MariaDB, openssh 7.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-60002 CVE-2026-60001 CVE-2026-60000 CVE-2026-59999 CVE-2026-59998 CVE-2026-59997 CVE-2026-59996 CVE-2026-59995 CVE-2026-35414 CVE-2026-35388 CVE-2026-35387 CVE-2026-35385 CVE-2025-32728 CVE-2025-26465 CVE-2023-51767 ...and 17 more
What to do
Confirm the running versions on 193.105.125.170 and compare them against the current security release for each package before treating any single CVE as live.
CVE-2026-60002 ↗CVE-2026-60001 ↗CVE-2026-60000 ↗CVE-2026-59999 ↗CVE-2026-59998 ↗
asset: 193.105.125.170
Database engines should sit behind a private network.
What to do
Restrict 3306/tcp to a VPN, bastion, or allow-listed source range.
asset: 193.105.125.170:3306
A visitor who types the address without https, or follows an old link, gets the unencrypted site. On public Wi-Fi that page can be read and rewritten in transit.
What to do
Redirect every http:// request to https:// with a 301, then add HSTS.
asset: https://hosting-warszawa.com/
Nothing tells receiving mail servers which hosts may send as @hosting-warszawa.com, so anyone can. Phishing that impersonates this domain will land in inboxes.
What to do
Publish an SPF TXT record listing your senders and ending in -all.
asset: hosting-warszawa.com
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.hosting-warszawa.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@hosting-warszawa.com"`, review the reports, then move to p=quarantine and p=reject.
asset: hosting-warszawa.com
193.105.125.170 (hosting-warszawa.com) reports exim 4.99.5, mariadb 10.6.19-MariaDB, openssh 7.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: 193.105.125.170
FTP transmits credentials in cleartext.
What to do
Restrict 21/tcp to a VPN, bastion, or allow-listed source range.
asset: 193.105.125.170:21
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: 193.105.125.170: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://hosting-warszawa.com/
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://hosting-warszawa.com/
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://hosting-warszawa.com/
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: hosting-warszawa.com
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: hosting-warszawa.com
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: hosting-warszawa.com

final https://hosting-warszawa.com/status 526time 763msstack cloudflare

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

✓Receives mail via 1 server
hosting-warszawa.com
✗SPF
no record
✗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
ns1.hosting-warszawa.com ns2.hosting-warszawa.com

✓Registered with PDR Ltd. d/b/a PublicDomainRegistry.com15.2 years old
hosting-warszawa.com
✓Registration expiry309 days
2027-07-13
✓Transfer lock
client transfer prohibited
✓2 nameservers at registry
ns1.hosting-warszawa.com ns2.hosting-warszawa.com

Address	Ports	CVEs	Edge	Network
193.105.125.170 hosting-warszawa.com +13	21225380110143443465+8	32	direct	—

Archived URLs

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

hosting-warszawa.com security report

Critical

Findings

Security headers

Email authentication

DNS

Registration

Hosts

Hostnames