Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
BReverse DNS0/4 IPs match cert SANREVIEW
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations171 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
BCDN & DeliveryAWS CloudFront (LambdaGeneratedResponse from cloudfront)REVIEW
BOperational Status PageNo status page link detectedREVIEW
BHealth Check EndpointNo conventional health endpoint foundREVIEW
A+DNS Records4 A records, 103 ms lookupPASS
| A | 13.249.231.78, 13.249.231.39, 13.249.231.36, 13.249.231.5 |
| AAAA | — |
| CNAME | — |
| NS | ns-1475.awsdns-56.org, ns-1919.awsdns-47.co.uk, ns-281.awsdns-35.com, ns-716.awsdns-25.net |
| MX | 0 aspmx.l.google.com 10 alt2.aspmx.l.google.com 10 alt1.aspmx.l.google.com 20 aspmx2.googlemail.com 20 aspmx3.googlemail.com |
| TXT | BSI84211529072 google-site-verification=OkNpCeDvzzDI9kMVtRLK0Hlgvo8AOBXj3Q24fUkhyEc google-site-verification=ei4cb-9YRgQTk9Z6KBxx3y77EM6rlMTB89IJEMxNNTQ SPF v=spf1 include:_spf.google.com ~all |
| CAA | Lookup not available with standard resolver |
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
AMulti-Resolver DNS SpeedMean 38ms across 3 resolvers (spread 96ms)PASS
ARedirect Chain1 redirect(s), 250 ms totalPASS
https://fanbyte.com
130 ms · HTTP/1.1
https://www.fanbyte.com/
120 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://fanbyte.com | 301 | 130 ms | HTTP/1.1 | CloudFront |
| 2 | https://www.fanbyte.com/ | 200 | 120 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 56 URLsPASS
User-agent: GPTBot
Disallow: /
User-agent: *
Allow: /
Disallow: /api/
Sitemap: https://www.fanbyte.com/sitemap/sitemap_index.xml
- https://www.fanbyte.com/sitemap/categori...
- https://www.fanbyte.com/sitemap/d2_items...
- https://www.fanbyte.com/sitemap/d2_items...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/ffxiv_it...
- https://www.fanbyte.com/sitemap/games-si...
- https://www.fanbyte.com/sitemap/homepage...
- https://www.fanbyte.com/sitemap/latest_p...
- https://www.fanbyte.com/sitemap/news-sit...
- https://www.fanbyte.com/sitemap/pages-si...
- https://www.fanbyte.com/sitemap/posts-si...
- https://www.fanbyte.com/sitemap/posts-si...
- https://www.fanbyte.com/sitemap/posts-si...
- https://www.fanbyte.com/sitemap/posts-si...
- https://www.fanbyte.com/sitemap/posts-si...
- https://www.fanbyte.com/sitemap/posts-si...
- https://www.fanbyte.com/sitemap/posts-si...
ADomain Intelligencefanbyte.com — via Amazon Registrar, Inc., 8 years, 11 months old, hosted on AWSPASS
66 days
July 20, 2026
171 days
Issued by Amazon
8 years, 11 months
Registered July 20, 2017
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
13.249.231.78
Amazon Registrar, Inc.
Expiry timeline
Recommended actions
- Renew the domain or enable auto-renewal to prevent accidental expiry
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Consider enabling auto-renewal to prevent accidental expiration.
Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.
Source: ICANN renewal policy
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