Skip to content
https://cookpad.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
95
GRADE
A
FIX
1
REVIEW
1
PASS
7
INFO
0
Probed from Madrid, Spain
302 Found
Checks
9
7 PASS 1 REVIEW 1 FIX
D
TLS Certificate Expiry & Recommendations
Action
10 days until leaf cert expires — 5 issues to address
FIX

Certificate validity

10
days left
0d 30d 60d 90d+
Renew urgently — under 14 days remaining

Recommended actions

  • Renew certificate — 10 days remaining
  • Add includeSubDomains to the HSTS directive
  • 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
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 2473 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 2473 B Sitemaps referenced 0 User-agents Timpibot, Baiduspider, Yandex, GPTBot, CCBot, Meta-ExternalAgent, GoogleOther, AI2Bot, Google-Extended, *, ClaudeBot, Omgilibot, Omgili, Diffbot, Peer39_crawler/1.0, Claude-Web, ImagesiftBot, PerplexityBot, Bytespider, Peer39_crawler, Applebot-Extended, ChatGPT-User, anthropic-ai, cohere-ai, FacebookBot Blocking No — crawling allowed
# See http://www.robotstxt.org/wc/norobots.html for documentation on how to use the robots.txt file
User-agent: *
Disallow: /user/confirm_premium_navi
Disallow: /*?_pxhc=*
Disallow: /*/recipes/*/reactions
Disallow: /*/recipes/*/similar_recipes
Disallow: /*/recipes/*/reactions
Disallow: /*/recipes/*/cooksnaps_section
Disallow: /*/recipes/*/print
Disallow: /*/activity_logs
Disallow: /*/service_feedbacks
Allow: /

User-agent: Baiduspider
Allow: /cn
Disallow: /cn/users
Disallow: /

User-agent: Yandex
Allow: /
Disallow: /*/accounts/new
Clean-param: epik&hl&noredir&find_method&hcb /ru/*
# See below for how Clean-param works for Yandex crawler
# https://yandex.ru/support/webmaster/robot-workings/clean-param.html?lang=en

# OpenAI Crawler
User-agent: GPTBot
Disallow: /

# OpenAI Plugin Bot
User-agent: ChatGPT-User
Disallow: /

# Block CCBot (used to create training datasets)
User-agent: CCBot
Disallow: /

# Anthropic AI bots
User-agent: anthropic-ai
Disallow: /

User-agent: Claude-Web
Disallow: /

User-agent: ClaudeBot
Disallow: /

# Enterprise LLM
User-agent: cohere-ai
Disallow: /

# Generates LLM datasets
User-agent: Omgilibot
Disallow: /
User-agent: Omgili
Disallow: /

# Default UA for a data scraping tool
User-agent: Diffbot
Disallow: /

# https://developers.facebook.com/docs/sharing/bot/
User-agent: FacebookBot
Disallow: /

# https://developers.facebook.com/docs/sharing/webmasters/web-crawlers
User-agent: Meta-ExternalAgent
Disallow: /

# Claims to be reverse image search, but is part of
# training dataset generator for https://hivemoderation.com
User-agent: ImagesiftBot
Disallow: /

# LLM Search
User-agent: PerplexityBot
Disallow: /

# TikTok generative LLM scraper
User-agent: Bytespider
Disallow: /

# Advertising tool / LLM
User-agent: Peer39_crawler
Disallow: /
User-agent: Peer39_crawler/1.0
Disallow: /

# AI Data Scraper
# https://darkvisitors.com/agents/timpibot
User-agent: Timpibot
Disallow: /

# Not related to Google Search etc
User-agent: GoogleOther
Disallow: /

# https://darkvisitors.com/agents/ai2bot
User-agent: AI2Bot
Disallow: /

###
# The following do not impact search results or functionality,
# but do tell the companies and bots in question
# not to add crawled content to LLM datasets.
######

# https://developers.google.com/search/docs/crawling-indexing/overview-google-crawlers#google-extended
User-agent: Google-Extended
Disallow: /

# https://support.apple.com/en-us/119829
User-agent: Applebot-Extended
Disallow: /

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

A+
DNS Records
4 A records, 142 ms lookup
PASS
4 A records, 142 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 151.101.193.55, 151.101.1.55, 151.101.65.55, 151.101.129.55
Info::
Has 4 IPv6 (AAAA) record(s)
Got: 2a04:4e42:600::311, 2a04:4e42::311, 2a04:4e42:200::311, 2a04:4e42:400::311
Info::
4 nameserver(s) configured
Got: ns-1805.awsdns-33.co.uk, ns-134.awsdns-16.com, ns-582.awsdns-08.net, ns-1526.awsdns-62.org
Info::
7 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 142 ms
Got: 142 ms
A151.101.193.55, 151.101.1.55, 151.101.65.55, 151.101.129.55
AAAA2a04:4e42:600::311, 2a04:4e42::311, 2a04:4e42:200::311, 2a04:4e42:400::311
CNAME
NSns-1805.awsdns-33.co.uk, ns-134.awsdns-16.com, ns-582.awsdns-08.net, ns-1526.awsdns-62.org
MX
10 aspmx.l.google.com
20 alt2.aspmx.l.google.com
20 alt1.aspmx.l.google.com
30 aspmx4.googlemail.com
30 aspmx5.googlemail.com
30 aspmx3.googlemail.com
30 aspmx2.googlemail.com
TXT
zapier-domain-verification-challenge=dd43c012-47e4-4d2a-bc2a-391b4e1c9fcc
facebook-domain-verification=ef8meu04yfkfpjri8bj4kkaaz0mcvo
docusign=97eb64ec-b3e3-4406-afa7-c55febaf89ad
google-site-verification=i1egF4TpFhWXX59S9njVn6Q1FHo0NhzibcSL_P-_KNQ
atlassian-domain-verification=QX2Lu9tptFEwXsSNfKL3p7oSIazgseY6XOLyFzKldyvFE4m65I...
_globalsign-domain-verification=rMzRmeoTKuY0aUkoQHHYV51XAmgXOv_4PqdRQ3a2AG
bill-one-domain-verification=128f8b17-6f0a-4e05-8295-818e20e6a788
pinterest-site-verification=600e3f9fd73486e001a8af1429cca6f0
jamf-site-verification=5BssqnQgjtfW3YPAAogEog
klaviyo-site-verification=W7BAnZ
docusign=05e8812d-22a2-4ed2-858c-fbf283d6ba33
ZOOM_verify_PJBrznrkl23C7pzFNLIAIS
google-site-verification=D1q8arJQYHaAz72JenFzPV-dJjfWpHgXzHVJYO9jxFw
anthropic-domain-verification-k6jvka=yjwJnlt1pQK8UKWZ4P47OsOjV
1password-site-verification=DV7C2SRZ7RFILITVF3ASFPZUK4
SPF v=spf1 include:fc1907.cuenote.jp include:_spf.google.com include:mail.zendesk.co...
apple-domain-verification=J13eN29gRx2ZgMwH
canva-site-verification=c9qI6oXpzdU-XzfCK2MTsg
google-site-verification=Br_vT7HTrFjXkPgotz8KNqUyitDpwoWck2FOgpBlUMw
asv=8b5615de832f55ca59d9632722fbeb05
cursor-domain-verification-cpn195=Wgx4UXCq78DSGM6pf5likSIBO
CAALookup not available with standard resolver
Resolved in 142 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
Redirect Chain
1 redirect(s), 244 ms total
PASS
1 redirect(s), 244 ms total
Info::
Single redirect
Got: https://cookpad.com → https://cookpad.com/jp (302)
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://cookpad.com

https://cookpad.com

4 ms · HTTP/1.1

302

https://cookpad.com/jp

240 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://cookpad.com3024 msHTTP/1.1Varnish
2https://cookpad.com/jp200240 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

A+
IPv6 Readiness
IPv6 reachable (0 ms)
PASS
IPv6 reachable (0 ms)
Info::
IPv6 is configured and reachable at 2a04:4e42:600::311, 2a04:4e42::311, 2a04:4e42:200::311, 2a04:4e42:400::311
Got: 0 ms connect
IPv6 Ready
AAAA Records 2a04:4e42:600::311, 2a04:4e42::311, 2a04:4e42:200::311, 2a04:4e42:400::311 Connection Reachable (0 ms)
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.cookpad.com/
200https://cookpad.com/

Preferred variant: non-www

HTTP → HTTPS

301http://cookpad.com/ https://cookpad.com/

Consistent

A+
Domain Intelligence
cookpad.com — via Network Solutions, LLC, 27 years, 5 months old
PASS
cookpad.com — via Network Solutions, LLC, 27 years, 5 months old
Info::
Domain registered until Apr 12, 2028 (2 years remaining)
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: Network Solutions, LLC
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.
Domain expiry

666 days

April 12, 2028

SSL certificate

10 days

Issued by Certainly

Domain age

27 years, 5 months

Registered April 12, 1999

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a04:4e42::311

Registrar

Network Solutions, LLC

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the TLS certificate or verify auto-renewal is working
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Network Solutions, LLC
Created April 12, 1999 (27 years, 5 months ago)
Expires April 12, 2028 (2 years)
Last Updated April 12, 2018
Name Servers ns-134.awsdns-16.com, ns-1526.awsdns-62.org, ns-1805.awsdns-33.co.uk, ns-582.awsdns-08.net
DNSSEC Not enabled
Hosting
IP Address 2a04:4e42::311
Data source: rdap (0.1s)

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 49 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
46 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
0 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
2 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
50 ms
Total Time Total request time from DNS lookup through full response.
50 ms

Connection waterfall

DNS Lookup 46 ms TCP Connect 0 ms TLS Handshake 2 ms Server Processing 2 ms Content Transfer 0 ms
A+
CDN & Delivery
Fastly (HIT)
PASS
Fastly (HIT)
Info::
Site is served via Fastly CDN
Got: x-served-by: cache-toj-leto2350077-TOJ
Info::
CDN cache status: HIT
CDN Detected: Fastly
Provider Fastly Cache Status HIT Evidence x-served-by: cache-toj-leto2350077-TOJ
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback