Built with WordPress and Inertia.js, hosted on Akamai Cloud (Linode) behind Cloudflare. Domain registered in 1998.
japantravel.com is built with WordPress, hosted on Akamai Cloud (Linode) behind Cloudflare. It measures traffic with Google Analytics and Google Tag Manager. It sends email through Amazon SES.
| Technology | Version | First seen |
|---|---|---|
| CMS & Site Builders1 | ||
| – | 16 Nov 2026 | |
| WordPress Plugins1 | ||
| – | 16 Nov 2026 | |
| JavaScript Frameworks & Libraries2 | ||
| – | 16 Nov 2026 | |
| Frontend Build Tools & CSS2 | ||
| 3.4.1 | 16 Nov 2026 | |
| Web Servers, Languages & Backend Frameworks2 | ||
| CDN & Hosting2 | ||
| – | 16 Nov 2026 | |
| Analytics & Tag Management2 | ||
| – | 16 Nov 2026 | |
| Advertising & Affiliate Tracking4 | ||
| – | 16 Nov 2026 | |
| Transactional Email1 | ||
| – | 16 Nov 2026 | |
| Fonts & Icon Fonts1 | ||
| – | 16 Nov 2026 | |
| Security, WAF & Bot Protection1 | ||
| – | 16 Nov 2026 | |
| Translation & Localization1 | ||
| – | 16 Nov 2026 | |
Registration from the registry's RDAP record, the certificate the site serves, and its rank in public traffic lists.
The crew hasn’t read this site’s colors yet. We read a palette when we capture a site’s screenshot, busiest sites first. Meanwhile, browse palettes from other sites.
What the homepage's first heading and body text render in, read from the browser's computed styles, and where the font files come from.
Counted from every stack change we've recorded: of the sites we watched running one of this site's tools, how many went on to add another. A pattern across sites, not a forecast for this one.
aspmx.l.google.comalt1.aspmx.l.google.comalt2.aspmx.l.google.comalt3.aspmx.l.google.comalt4.aspmx.l.google.comns2.japantravel.comns1.metroworks.co.jpns2.metroworks.co.jpns1.japantravel.comMS=ms89769201google-site-verification=DfPKK2p7eCVCM_xKMVzh6CxuxzNIOhsFr3IoagLg6aUv=spf1 ip4:45.33.59.59 ip6:2600:3c01::f03c:91ff:fe81:9cd2 ip4:139.162.81.108 ip6:2400:8902::f03c:91ff:fed0:a6c9 ip4:172.237.19.198 ip6:2600:3c18::f03c:95ff:fe29:158c ip4:139.162.124.25 ip6:2400:8902::f03c:93ff:fe9a:bf90 ip4:116.202.85.209 ip6:2a01:4f8:231:3ee0::1 include:_spf.google.com -allamazonses:LImQLLIr8XfVd9HJVh538rrVKsrpLuJETK1AK3Ot3Ig=google-site-verification=zUjuhiU5TD2KmlWwPfaNKXwmMXOITL2TgNhNmnVggZIv=DMARC1; p=reject; rua=mailto:kuijtegv@ag.jp.dmarcian.com; ruf=mailto:kuijtegv@fr.jp.dmarcian.com; adkim=r; aspf=r; rf=afrf# AI answer engines - ALLOWED (ACQ3-1486). These crawlers fetch a page to answer a # live user question and link back to us; they do not harvest content for model # training. The training crawlers further down stay blocked. # # A named group does NOT inherit `User-agent: *` - a crawler obeys only the most # specific group matching its name and ignores every other group. The ACQ3-1256 # paths are therefore repeated here; without them these crawlers would walk /search # and /api/, which bypass the Layer 2 response cache and fan out to expensive # backend queries. # # This does NOT unblock them from /auth/sso/redirect: public/.htaccess and the # BlockBotSsoRedirect middleware still 403 these user agents on that one route # (ACQ3-1091 - bots don't persist cookies, so every hit created a fresh Redis # session). Letting a crawler read our pages is not letting it start login # sessions. Do not "sync" those two lists with this file. User-agent: OAI-SearchBot User-agent: ChatGPT-User User-agent: PerplexityBot User-agent: Perplexity-User User-agent: Claude-SearchBot User-agent: Claude-User Disallow: /search Disallow: /search/ Disallow: /search? Disallow: /auth/ Disallow: /api/ Disallow: /index.php # AI / LLM training crawlers — blocked due to load and zero SEO benefit User-agent: GPTBot Disallow: / User-agent: ClaudeBot Disallow: / User-agent: Claude-Web Disallow: / User-agent: anthropic-ai Disallow: / User-agent: Google-Extended Disallow: / User-agent: Bytespider Disallow: / User-agent: CCBot Disallow: / User-agent: cohere-ai Disallow: / User-agent: Diffbot Disallow: / User-agent: FacebookBot Disallow: / User-agent: meta-externalagent Disallow: / User-agent: Meta-ExternalAgent Disallow: / User-agent: Meta-ExternalFetcher Disallow: / User-agent: Applebot-Extended Disallow: / User-agent: Amazonbot Disallow: / User-agent: YouBot Disallow: / User-agent: Omgilibot Disallow: / User-agent: omgili Disallow: / User-agent: ImagesiftBot Disallow: / User-agent: img2dataset Disallow: / User-agent: PetalBot Disallow: / User-agent: Timpibot Disallow: / User-agent: Kangaroo Bot Disallow: / User-agent: Scrapy Disallow: / User-agent: TLM-Audit-Scanner Disallow: / # Aggressive SEO scrapers — blocked due to high request volume User-agent: SemrushBot Disallow: / User-agent: AhrefsBot Disallow: / User-agent: MJ12bot Disallow: / User-agent: DotBot Disallow: / User-agent: BLEXBot Disallow: / User-agent: DataForSeoBot Disallow: / User-agent: YisouSpider Disallow: / User-agent: Yisouspider Disallow: / # High-volume crawler — blocked (was ~329k req/day from 8 AWS IPs re-fetching # the same static assets thousands of times each, incident 2026-06-01). # Pinterest honors robots.txt, so Disallow should stop it. User-agent: Pinterestbot Disallow: / # Default — allow legitimate search engines (Googlebot, Bingbot, etc.) # but disallow search-result pages and internal AJAX/legacy endpoints from # being crawled (no SEO value, expensive). ACQ3-1256: Googlebot was walking # /api/* XHR endpoints and /index.php-prefixed legacy URLs, both of which # bypass the Layer 2 response cache and fan out to expensive backend queries. User-agent: * Disallow: /search Disallow: /search/ Disallow: /search? Disallow: /auth/ Disallow: /api/ Disallow: /index.php
| – |
| 16 Nov 2026 |
| – |
| 16 Nov 2026 |
| – |
| 16 Nov 2026 |
| – | 16 Nov 2026 |
| – |
| 16 Nov 2026 |
| – |
| 16 Nov 2026 |
| – |
| 16 Nov 2026 |
| – | 16 Nov 2026 |
| – | 16 Nov 2026 |