Skip to content
https://hotpepper.jp

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Singapore, Singapore
302 Found
Checks
9
4 PASS 4 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 204 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 204 B Sitemaps referenced 0 User-agents *, bingbot, Slurp Blocking No — crawling allowed
User-agent: *

Disallow: /gourmetnotes/

Disallow: /CSP/

Disallow: /doc/rp/

Disallow: /*/fwt*


Allow: /CSP/api/recommend/


User-agent: bingbot

Crawl-delay: 10

User-agent: Slurp

Crawl-delay: 1

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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.hotpepper.jp/
200https://hotpepper.jp/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://hotpepper.jp/ https://hotpepper.jp/

Consistent

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

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • 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
A+
DNS Records
1 A records, 153 ms lookup
PASS
1 A records, 153 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 160.17.98.198
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns2.x.recruit.co.jp, ns3.x.recruit.co.jp, ns1.x.recruit.co.jp
Info::
1 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: 153 ms
Got: 153 ms
A160.17.98.198
AAAA
CNAME
NSns2.x.recruit.co.jp, ns3.x.recruit.co.jp, ns1.x.recruit.co.jp
MX
10 mx.x.recruit.co.jp
TXT
SPF v=spf1 include:spf01.hotpepper.jp include:spf-bma.rec.mpme.jp include:spf.tricor...
google-site-verification=SNmKrEQm3WMJpdGEDJZ_N5ulmP_CwNEiwE0AFeYVjuU
CAALookup not available with standard resolver
Resolved in 153 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

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), 684 ms total
PASS
1 redirect(s), 684 ms total
Info::
Single redirect
Got: https://hotpepper.jp → https://www.hotpepper.jp/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://hotpepper.jp
Info::
Redirect overhead: 684 ms total
Got: 684 ms

https://hotpepper.jp

385 ms · HTTP/1.1

302

https://www.hotpepper.jp/

299 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://hotpepper.jp302385 msHTTP/1.1Apache
2https://www.hotpepper.jp/200299 msHTTP/1.1Apache

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+
Domain Intelligence
hotpepper.jp — hosted on IIJ Internet Initiative Japan Inc., JP
PASS
hotpepper.jp — hosted on IIJ Internet Initiative Japan Inc., JP
Info::
Hosting: IIJ Internet Initiative Japan Inc., JP
Got: AS2497
Domain expiry

Unknown

SSL certificate

268 days

Issued by DigiCert Inc

Domain age

Unknown

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

IIJ Internet Initiative Japan Inc., JP

ASN AS2497

160.17.98.198

Registrar

Registrar unknown

Lock status unknown 3 NS records
Expiry timeline
Today
+1 year
SSL expiry Danger zone (≤30 days)
Registrar
Name Servers ns1.x.recruit.co.jp, ns2.x.recruit.co.jp, ns3.x.recruit.co.jp
Hosting
IP Address 160.17.98.198
ASN AS2497 (IIJ Internet Initiative Japan Inc., JP)
Provider IIJ Internet Initiative Japan Inc., JP
Data source: whois (1.5s)
A+
HTTP Probe Timing
Total 355 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
78 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
69 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
139 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
355 ms
Total Time Total request time from DNS lookup through full response.
356 ms

Connection waterfall

DNS Lookup 78 ms TCP Connect 69 ms TLS Handshake 139 ms Server Processing 69 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback