Skip to content
https://fanbyte.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
9
PASS
8
INFO
0
Probed from Singapore, Singapore
301 Moved Permanently
Checks
17
8 PASS 9 REVIEW
B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
B
Reverse DNS
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR for 13.249.231.78 does not match any cert SAN: server-13-249-231-78.sin3.r.cloudfront.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 13.249.231.39 does not match any cert SAN: server-13-249-231-39.sin3.r.cloudfront.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 13.249.231.36 does not match any cert SAN: server-13-249-231-36.sin3.r.cloudfront.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 13.249.231.5 does not match any cert SAN: server-13-249-231-5.sin3.r.cloudfront.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.fanbyte.com/
200https://fanbyte.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://fanbyte.com/ https://fanbyte.com/

Consistent

B
TLS Certificate Expiry & Recommendations
171 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

171
days left
0d 30d 60d 90d+

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
B
CDN & Delivery
AWS CloudFront (LambdaGeneratedResponse from cloudfront)
REVIEW
AWS CloudFront (LambdaGeneratedResponse from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: SIN3-P5)
Got: x-amz-cf-id: hXgx2slyj22mKS_PPq5fWUnBQDRM__BMOY_K-1LbxnIjTCvEctRuDA==
Info::
CDN cache status: LambdaGeneratedResponse from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status LambdaGeneratedResponse from cloudfront Evidence x-amz-cf-id: hXgx2slyj22mKS_PPq5fWUnBQDRM__BMOY_K-1LbxnIjTCvEctRuDA==
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
DNS Records
4 A records, 103 ms lookup
PASS
4 A records, 103 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 13.249.231.78, 13.249.231.39, 13.249.231.36, 13.249.231.5
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1475.awsdns-56.org, ns-1919.awsdns-47.co.uk, ns-281.awsdns-35.com, ns-716.awsdns-25.net
Info::
5 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 103 ms
Got: 103 ms
A13.249.231.78, 13.249.231.39, 13.249.231.36, 13.249.231.5
AAAA
CNAME
NSns-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
CAALookup not available with standard resolver
Resolved in 103 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A
Multi-Resolver DNS Speed
Mean 38ms across 3 resolvers (spread 96ms)
PASS
Mean 38ms across 3 resolvers (spread 96ms)
Info::
Google: 6ms
Got: 6ms via 8.8.8.8:53
Info::
Quad9: 8ms
Got: 8ms via 9.9.9.9:53
Info::
Cloudflare: 102ms
Got: 102ms via 1.1.1.1:53
A
Redirect Chain
1 redirect(s), 250 ms total
PASS
1 redirect(s), 250 ms total
Info::
Single redirect
Got: https://fanbyte.com → https://www.fanbyte.com/ (301)
Info::
WWW normalization redirect

https://fanbyte.com

130 ms · HTTP/1.1

301

https://www.fanbyte.com/

120 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://fanbyte.com301130 msHTTP/1.1CloudFront
2https://www.fanbyte.com/200120 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 56 URLs
PASS
robots.txt present, sitemap with 56 URLs
Info::
robots.txt is present
Got: 130 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 56 entries
Info::
Sitemap index with 56 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 130 B Sitemaps referenced 1 User-agents GPTBot, * Blocking No — crawling allowed
User-agent: GPTBot
Disallow: /

User-agent: *
Allow: /
Disallow: /api/

Sitemap: https://www.fanbyte.com/sitemap/sitemap_index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 56 entries Valid XML Yes
Child Sitemaps:
A
Domain Intelligence
fanbyte.com — via Amazon Registrar, Inc., 8 years, 11 months old, hosted on AWS
PASS
fanbyte.com — via Amazon Registrar, Inc., 8 years, 11 months old, hosted on AWS
Warning::
Domain expires in 71 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jul 20, 2026
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Amazon Registrar, Inc.
Warning::
Registrar lock is NOT enabled
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.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

66 days

July 20, 2026

SSL certificate

171 days

Issued by Amazon

Domain age

8 years, 11 months

Registered July 20, 2017

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

13.249.231.78

Registrar

Amazon Registrar, Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
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
Registrar Amazon Registrar, Inc.
Created July 20, 2017 (8 years, 11 months ago)
Expires July 20, 2026 (2 months)
Last Updated June 15, 2025
Name Servers ns-1475.awsdns-56.org, ns-1919.awsdns-47.co.uk, ns-281.awsdns-35.com, ns-716.awsdns-25.net
DNSSEC Not enabled
Hosting
IP Address 13.249.231.78
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.4s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

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.

Why this matters

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.

Why this matters

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

A+
HTTP Probe Timing
Total 130 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
103 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
2 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
8 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
130 ms
Total Time Total request time from DNS lookup through full response.
130 ms

Connection waterfall

DNS Lookup 103 ms TCP Connect 2 ms TLS Handshake 8 ms Server Processing 17 ms Content Transfer 0 ms
A+
CDN Cache Observability
Cache state: LAMBDAGENERATEDRESPONSE
PASS
Cache state: LAMBDAGENERATEDRESPONSE
Info::
CDN cache state observable via 1 header(s)
Got: x-cache=LambdaGeneratedResponse from cloudfront
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback