Infrastructure - https://foodnetwork.com BeaverCheck Audit

F

Redirect Chain

Action

4 redirect(s), 205 ms total

FIX

4 redirect(s), 205 ms total

4 redirects before reaching final URL

Each redirect adds latency. Try to minimize the chain to 1 hop.

HTTP to HTTPS redirect present

WWW normalization redirect

4-hop chain could be reduced to 1 hop

Redirect directly from https://foodnetwork.com to https://foodnetwork.co.uk/?utm_source=foodnetwork.com&utm_medium=domestic

Cross-domain redirect detected

https://foodnetwork.com

12 ms · HTTP/1.1

301

https://www.foodnetwork.com:443/

74 ms · HTTP/1.1

301

http://www.foodnetwork.co.uk/?utm_source...

30 ms · HTTP/1.1

301

https://www.foodnetwork.co.uk/?utm_sourc...

46 ms · HTTP/1.1

301

https://foodnetwork.co.uk/?utm_source=fo...

44 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://foodnetwork.com	301	12 ms	HTTP/1.1	awselb/2.0
2	https://www.foodnetwork.com:443/	301	74 ms	HTTP/1.1
3	http://www.foodnetwork.co.uk/?utm_source...	301	30 ms	HTTP/1.1	Varnish
4	https://www.foodnetwork.co.uk/?utm_sourc...	301	46 ms	HTTP/1.1
5	https://foodnetwork.co.uk/?utm_source=fo...	200	44 ms	HTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

Redirect directly from https://foodnetwork.com to https://foodnetwork.co.uk/?utm_source=foodnetwork.com&utm_medium=domestic

Why this matters

Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.

Source: web.dev

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

234 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

234

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

A+

DNS Records

4 A records, 183 ms lookup

PASS

4 A records, 183 ms lookup

Resolves to 4 IPv4 address(es)

Got: 65.8.202.16, 65.8.202.12, 65.8.202.59, 65.8.202.2

No IPv6 (AAAA) records

4 nameserver(s) configured

Got: ns-788.awsdns-34.net, ns-1657.awsdns-15.co.uk, ns-298.awsdns-37.com, ns-1126.awsdns-12.org

1 mail exchanger(s) configured

CAA records not checked

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

SPF record present in TXT

DNS resolution time: 183 ms

Got: 183 ms

A	65.8.202.16, 65.8.202.12, 65.8.202.59, 65.8.202.2
AAAA	—
CNAME	—
NS	ns-788.awsdns-34.net, ns-1657.awsdns-15.co.uk, ns-298.awsdns-37.com, ns-1126.awsdns-12.org
MX	10 foodnetwork-com.mail.protection.outlook.com
TXT	google-site-verification=gc9Ips1tSxJLxOXs0wMURIl1kGqg9ws1Q3gcnXwRQrM _q0hslyb8ci8s55oe5v88cbthj8usqzh _globalsign-domain-verification=HesdCl7p3f9VfRfjcqSFnpiLQa9vvBQdS5Y6t_P7kR _globalsign-domain-verification=yZG2iEZOIsISFdl-eGm5P7KjD6GEVwn8OIeopyR6_y SPF v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all google-site-verification=1FgZjswEcgnM1CMlEuXLyJCW7Yjw3pgCcTzK_qyFtlc atlassian-domain-verification=joqe6L8dNi+aisGbB1XHQa0pDc53V2l0GQQRUtLEcr2997x0+r... d1uz6fhu10tkxd.cloudfront.net google-site-verification=qhFG8kE2DfUpjhgq95qFtX-SFDDUyZYOAtDHTuH8CgI 1zc4cr50d51xyh1xtg07dj163gn5wg0v 0b4g2mx25tg4410kmj5gr5y75w4dmg67 MS=ms68089283 1vWa8J1FHuS3mbRkpagKiMZ42WG1XghtSgb0UEUA8Nsz9evLF4Wr69iaS0o0 _globalsign-domain-verification=XFxYnL9aJP8nREVcfqj9aHXTEpRMn0veiOt4-Xv2fK _globalsign-domain-verification=_1TbuR5NWsxbqZeT5ADgz1XPI-Z_deTwPMhZAqluQ- d3fnwmkemxdgbz.cloudfront.net MS=ms90829515 _globalsign-domain-verification=IoYldELUwIPqrgAukpxs-t0k7wTGoaWYLZqZTNMktA google-site-verification=QW1cwRZx-2tzGgtB2I3BQ7YZRef4tE_Va0zjpz91qzo google-site-verification=YKb5Ib9dp-mf6uPyj95FPUVCJQ6wOFXeaAoz77MOzE4 _globalsign-domain-verification=BY4YeBu-GWgUs62c-D84Izvv3YCwDtUvHceyFIbTiL facebook-domain-verification=2x5alsxpaddw3sjbck12xque11vyad
CAA	Lookup not available with standard resolver

Resolved in 183 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A+

Crawlability

robots.txt present, sitemap with 20 URLs

PASS

robots.txt present, sitemap with 20 URLs

robots.txt is present

Got: 202 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 20 entries

Sitemap index with 20 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

Size 202 B Sitemaps referenced 1 User-agents MJ12Bot, *, PetalBot Blocking No — crawling allowed

User-agent: *
Disallow: /?=*
Sitemap: https://foodnetwork.co.uk/sitemaps/sitemap.xml

# Block PetalBot
User-agent: PetalBot
Disallow: /

# Block MJ12Bot
User-agent: MJ12Bot
Disallow: /

Crawl-delay: 60

sitemap.xml 200 OK

Type Sitemap Index URLs 20 entries Valid XML Yes

Child Sitemaps:

A+

URL Variants

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

PASS

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

HTTP correctly 301-redirects to HTTPS

www / non-www

403https://www.foodnetwork.com/

200https://foodnetwork.com/

HTTP → HTTPS

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

Consistent

A+

Domain Intelligence

foodnetwork.com — via Nom-iq Ltd. dba COM LAUDE, 30 years, 7 months old, hosted on AWS

PASS

foodnetwork.com — via Nom-iq Ltd. dba COM LAUDE, 30 years, 7 months old, hosted on AWS

Domain registered until Feb 26, 2027 (10 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: Nom-iq Ltd. dba COM LAUDE

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: AWS

Got: AS16509

Domain expiry

257 days

February 26, 2027

SSL certificate

234 days

Issued by Amazon

Domain age

30 years, 7 months

Registered February 25, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

65.8.202.59

Registrar

Nom-iq Ltd. dba COM LAUDE

Unlocked 4 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 Nom-iq Ltd. dba COM LAUDE

Created February 25, 1996 (30 years, 7 months ago)

Expires February 26, 2027 (10 months)

Last Updated February 6, 2026

Name Servers ns-1126.awsdns-12.org, ns-1657.awsdns-15.co.uk, ns-298.awsdns-37.com, ns-788.awsdns-34.net

DNSSEC Not enabled

Hosting

IP Address 65.8.202.59

ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)

Provider AWS

Data source: rdap (0.3s)

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

PASS

DNS Lookup

32 ms

TCP Connect

1 ms

TLS Handshake

5 ms

Time to First Byte

43 ms

Total Time

43 ms

Connection waterfall

DNS Lookup 32 ms TCP Connect 1 ms TLS Handshake 5 ms Server Processing 5 ms Content Transfer 0 ms

A+

CDN & Delivery

AWS CloudFront (Hit from cloudfront)

PASS

AWS CloudFront (Hit from cloudfront)

Site is served via AWS CloudFront CDN (edge: MAD56-P6)

Got: x-amz-cf-id: adRanoM2wsJnHKpbaASJxIhUylxUm2zpMEdrweaitCCWKNFh0o0huA==

CDN cache status: Hit from cloudfront

CDN Detected: AWS CloudFront

Provider AWS CloudFront Cache Status Hit from cloudfront Evidence x-amz-cf-id: adRanoM2wsJnHKpbaASJxIhUylxUm2zpMEdrweaitCCWKNFh0o0huA==