Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.FIPv6 ReadinessActionIPv6 records exist but unreachableFIX
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.
Learn more ▾ ▴
Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.
Source: RFC 8305 (Happy Eyeballs)
BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
CReverse DNSAction0/4 IPs match cert SANREVIEW
BTLS Certificate Expiry & Recommendations60 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
- Enable DNSSEC on your domain for DNS spoofing protection
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
BOperational Status PageNo status page link detectedREVIEW
A+DNS Records2 A records, 18 ms lookupPASS
| A | 172.67.171.62, 104.21.29.16 |
| AAAA | 2606:4700:3035::ac43:ab3e, 2606:4700:3030::6815:1d10 |
| CNAME | — |
| NS | lee.ns.cloudflare.com, liberty.ns.cloudflare.com |
| MX | 28 route3.mx.cloudflare.net 61 route2.mx.cloudflare.net 73 route1.mx.cloudflare.net |
| TXT | google-site-verification=y2N3nJoln8ExKRgKG8xttnadSu_B8OXgOI80JNNJghg SPF v=spf1 include:_spf.mx.cloudflare.net ~all yandex-verification: 42d26d0170fcd3ff |
| CAA | Lookup not available with standard resolver |
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
A+Multi-Resolver DNS SpeedMean 7ms across 3 resolvers (spread 11ms)PASS
A+Redirect ChainNo redirects — direct accessPASS
https://m3u8-player.net
101 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://m3u8-player.net | 200 | 101 ms | HTTP/1.1 | cloudflare |
A+Crawlabilityrobots.txt present, sitemap with 1 URLsPASS
# *
User-agent: *
Allow: /
Disallow: /api/
Disallow: /admin/
Disallow: /console/
Disallow: /auth/
Disallow: /signin/
Disallow: /signup/
# Googlebot
User-agent: Googlebot
Allow: /
Disallow: /api/
Disallow: /admin/
Disallow: /console/
Disallow: /auth/
Disallow: /signin/
Disallow: /signup/
# Bingbot
User-agent: Bingbot
Allow: /
Disallow: /api/
Disallow: /admin/
Disallow: /console/
Disallow: /auth/
Disallow: /signin/
Disallow: /signup/
# Yandex
User-agent: Yandex
Allow: /
Disallow: /api/
Disallow: /admin/
Disallow: /console/
Disallow: /auth/
Disallow: /signin/
Disallow: /signup/
# Baiduspider
User-agent: Baiduspider
Allow: /
Disallow: /api/
Disallow: /admin/
Disallow: /console/
Disallow: /auth/
Disallow: /signin/
Disallow: /signup/
# Host
Host: https://m3u8-player.net
# Sitemaps
Sitemap: https://m3u8-player.net/sitemap.xml
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencem3u8-player.net — via NameCheap, Inc., 11 months oldPASS
378 days
September 9, 2027
60 days
Issued by Google Trust Services
11 months
Registered September 9, 2025
Not enabled
Protects against DNS spoofing
Unknown
2606:4700:3030::6815:1d10
NameCheap, Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.
Learn more ▾ ▴
DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.
Source: ICANN / RFC 4033
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.
Learn more ▾ ▴
Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.
Source: ICANN / domain-security best practice