tenislive.pl security report

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

64risk

Elevated

Several issues worth triaging this week.

0Critical

3High

1Medium

1Low

2Info

Collected 2 hours ago6.9sfrom cache

Domain—

unavailable

Certificate Transparency2
DNS resolution4
Network ownership0
CDN / WAF detection0
Exposed ports & CVEs26
Registration
DNS posture2
Email authentication0
Certificate
Security headers5
Archived URLs
Analysis7

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 429). Results below are partial.
note2 hosts were identified as CDN/edge infrastructure from ASN ownership rather than a cdncheck fingerprint.

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://tenislive.pl/
Nothing tells receiving mail servers which hosts may send as @tenislive.pl, 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: tenislive.pl
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.tenislive.pl TXT "v=DMARC1; p=none; rua=mailto:dmarc@tenislive.pl"`, review the reports, then move to p=quarantine and p=reject.
asset: tenislive.pl
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://tenislive.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: tenislive.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: tenislive.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: tenislive.pl

final https://tenislive.pl/status 403time 25msstack cloudflare

✗http:// redirects to https://
✗Strict-Transport-Security
✓Content-Security-Policy
default-src 'none'; script-src 'nonce-4cug7Mw9eZGc0tk3C0gdEg' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'…
✓Clickjacking protection
SAMEORIGIN
✓X-Content-Type-Options
nosniff
✓Referrer-Policy
same-origin
✓Permissions-Policy
accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),micro
–security.txt publishedoptional — tells researchers where to report bugs

✓Receives mail via 1 server
mail.tenislive.pl
✗SPF
no record
✗DMARC
no record
!MTA-STSinbound mail can be downgraded to plaintext

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

Address	Ports	CVEs	Edge	Network
172.67.211.39 tenislive.pl +3	80443205220532082208320862087+5	0	Cloudflare~	—
104.21.83.38 tenislive.pl +3	80443205220532082208320862087+5	0	Cloudflare~	—

Archived URLs

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

tenislive.pl security report

Elevated

Findings

Security headers

Email authentication

DNS

Hosts

Hostnames