Infrastructure - https://fantasyteamadvice.com BeaverCheck Audit

B

DNSSEC

Unsigned (DNSSEC not deployed)

REVIEW

Unsigned (DNSSEC not deployed)

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)

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.

C

Reverse DNS

Action

0/1 IPs match cert SAN

REVIEW

0/1 IPs match cert SAN

PTR lookup failed for 216.24.57.1: lookup 216.24.57.1: no such host

No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

C

IPv6 Readiness

Action

No IPv6 support

REVIEW

No IPv6 support

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

TLS Certificate Expiry & Recommendations

88 days until leaf cert expires — 2 issues to address

REVIEW

Certificate validity

88

days left

0d 30d 60d 90d+

Recommended actions

Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
Enable DNSSEC on your domain for DNS spoofing protection

B

Operational Status Page

No status page link detected

REVIEW

No status page link detected

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

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: 429, /health: 429, /healthz: 429, /ping: 429, /status: 429.

A+

DNS Records

1 A records, 37 ms lookup

PASS

1 A records, 37 ms lookup

Resolves to 1 IPv4 address(es)

Got: 216.24.57.1

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

2 nameserver(s) configured

Got: dns1.registrar-servers.com, dns2.registrar-servers.com

1 mail exchanger(s) configured

SPF record present in TXT

DNS resolution time: 37 ms

Got: 37 ms

A	216.24.57.1
AAAA	—
CNAME	—
NS	dns1.registrar-servers.com, dns2.registrar-servers.com
MX	10 inbound-smtp.us-west-2.amazonaws.com
TXT	SPF v=spf1 include:amazonses.com ~all
CAA	Lookup not available with standard resolver

Resolved in 37 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

A+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

No CNAME record present

A+

Multi-Resolver DNS Speed

Mean 31ms across 3 resolvers (spread 22ms)

PASS

Mean 31ms across 3 resolvers (spread 22ms)

Cloudflare: 23ms

Got: 23ms via 1.1.1.1:53

Google: 25ms

Got: 25ms via 8.8.8.8:53

Quad9: 45ms

Got: 45ms via 9.9.9.9:53

A+

Redirect Chain

No redirects — direct access

PASS

No redirects — direct access

Got: https://fantasyteamadvice.com

https://fantasyteamadvice.com

256 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://fantasyteamadvice.com	200	256 ms	HTTP/1.1	cloudflare

A+

Crawlability

robots.txt present, sitemap with 5 URLs

PASS

robots.txt present, sitemap with 5 URLs

robots.txt is present

Got: 2298 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 5 entries

Sitemap index with 5 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

Size 2298 B Sitemaps referenced 1 User-agents Google-Extended, Applebot-Extended, meta-externalagent, ChatGPT-User, OAI-SearchBot, Amazonbot, YouBot, CCBot, *, GPTBot, ClaudeBot, Claude-Web, PerplexityBot, Perplexity-User, cohere-ai, anthropic-ai, Diffbot, ImagesiftBot, DotBot, Bytespider Blocking No — crawling allowed

# See https://www.robotstxt.org/robotstxt.html for documentation on how to use the robots.txt file

# Allow all crawlers by default (Googlebot, Bingbot, DuckDuckBot, social-preview
# bots, etc.) so search engines can still index our public pages.
User-agent: *
Allow: /

# Disallow admin and private areas
Disallow: /admin/
Disallow: /users/
Disallow: /letter_opener/
Disallow: /mission-control/
Disallow: /jobs/
Disallow: /test/

# Keep the in-page search and pagination URLs out of the index; the pages
# themselves also emit `<meta name="robots" content="noindex, follow">`.
Disallow: /funny-fantasy-football-team-names*?q=
Disallow: /funny-fantasy-football-team-names*&q=

# Block known AI-training / LLM-answer-engine crawlers from the entire site.
# These bots fetch our pages to train or serve LLMs without sending users back
# to us, so there is no upside to letting them in. They respect robots.txt and
# rotate IPs heavily, which makes IP-level bans ineffective — robots.txt is the
# authoritative opt-out mechanism. Keep this list in sync with BotDetector's
# `ai_scraper: true` signatures in app/services/bot_detector.rb.

User-agent: GPTBot
Disallow: /

User-agent: ChatGPT-User
Disallow: /

User-agent: OAI-SearchBot
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: anthropic-ai
Disallow: /

User-agent: Claude-Web
Disallow: /

User-agent: PerplexityBot
Disallow: /

User-agent: Perplexity-User
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: meta-externalagent
Disallow: /

User-agent: Amazonbot
Disallow: /

User-agent: cohere-ai
Disallow: /

User-agent: Diffbot
Disallow: /

User-agent: ImagesiftBot
Disallow: /

User-agent: YouBot
Disallow: /

# Block DotBot (Moz's OpenSiteExplorer crawler). We've been seeing it fan out
# across hundreds of distinct IPs per hour on /admin/bot-activity, which looks
# like a residential-proxy botnet impersonating the UA rather than Moz itself.
# Either way we don't need the backlink data, so the simplest fix is to tell
# well-behaved DotBot clients to stay out and rely on edge blocks for the rest.
User-agent: DotBot
Disallow: /

# Sitemap location
Sitemap: https://fantasyteamadvice.com/sitemap.xml

sitemap.xml 200 OK

Type Sitemap Index URLs 5 entries Valid XML Yes

Child Sitemaps:

A+

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

PASS

www/non-www, trailing slash, HTTP→HTTPS

www/non-www redirect configured correctly (preferred: non-www)

HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.fantasyteamadvice.com/

200https://fantasyteamadvice.com/

Preferred variant: non-www

HTTP → HTTPS

301http://fantasyteamadvice.com/ → https://fantasyteamadvice.com/

Consistent

A+

Domain Intelligence

fantasyteamadvice.com — via NameCheap, Inc., 14 years, 7 months old, hosted on RENDER - Render, US

PASS

fantasyteamadvice.com — via NameCheap, Inc., 14 years, 7 months old, hosted on RENDER - Render, US

Domain registered until Dec 9, 2026 (7 months remaining)

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.

Registrar: NameCheap, Inc.

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.

Hosting: RENDER - Render, US

Got: AS397273

Domain expiry

206 days

December 9, 2026

SSL certificate

88 days

Issued by Google Trust Services

Domain age

14 years, 7 months

Registered December 9, 2011

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

RENDER - Render, US

ASN AS397273

216.24.57.1

Registrar

NameCheap, Inc.

Unlocked 2 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Enable DNSSEC to protect visitors from DNS spoofing
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar NameCheap, Inc.

Created December 9, 2011 (14 years, 7 months ago)

Expires December 9, 2026 (7 months)

Last Updated January 11, 2026

Name Servers dns1.registrar-servers.com, dns2.registrar-servers.com

DNSSEC Not enabled

Hosting

IP Address 216.24.57.1

ASN AS397273 (RENDER - Render, US)

Provider RENDER - Render, US

Data source: rdap (0.4s)

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 306 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

PASS

DNS Lookup

37 ms

TCP Connect

1 ms

TLS Handshake

8 ms

Time to First Byte

300 ms

Total Time

307 ms

Connection waterfall

DNS Lookup 37 ms TCP Connect 1 ms TLS Handshake 8 ms Server Processing 254 ms Content Transfer 7 ms

A

CDN & Delivery

Cloudflare (DYNAMIC)

PASS

Cloudflare (DYNAMIC)

Site is served via Cloudflare CDN (edge: MAD)

Got: cf-ray: 9f996532893b86f7-MAD

CDN cache status: DYNAMIC

CDN Detected: Cloudflare

Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: 9f996532893b86f7-MAD

A+

CDN Cache Observability

Cache state: DYNAMIC

PASS

Cache state: DYNAMIC

CDN cache state observable via 1 header(s)

Got: cf-cache-status=DYNAMIC