Quick read
How to read aurelie.tokyo quickly
aurelie.tokyo looks like style & fashion. Traffic signals point to roughly 145.0K monthly visits. Current AI trust scoring is 15/100.
What to do next
- The stack appears to include Unknown.
- Open the Traffic tab if you need audience scale and geography before outreach.
- Open the Business tab if trust, monetization, or positioning is your first decision filter.
Provider Completeness
51/56 fields populated (91%)
Providers with missing fields
View field-level status
visual: 4/4
All expected fields present
meta: 3/3
All expected fields present
seo: 5/5
All expected fields present
dns: 4/4
All expected fields present
ads: 5/5
All expected fields present
publisher: 3/5
Missing: directCount, resellerCount
files: 2/3
Missing: robotsSitemapUrls
traffic: 10/10
All expected fields present
whois: 6/6
All expected fields present
radar: 2/4
Missing: categories, sourceTimestamp
ai: 7/7
All expected fields present
Why this module matters
Technology data helps you qualify implementation maturity
This section shows what the site appears to run on, which providers support it, and whether the technical footprint looks modern, stable, and discoverable.
- Stack tags are useful for sales, partnerships, and benchmarking.
- DNS and files help you judge operational hygiene.
- Provider health and timing reveal how complete the current read is.
Technology Stack
Infrastructure
DNS Provider
Mail Exchange
NS Records
TXT Records
"google-site-verification=_yTHoQpEhC33KJH-12QgnN8DYBqLV0VICx8HvfQuSQs"
"v=spf1 include:amazonses.com ip4:3.115.209.151 include:spf-bma.mpme.jp include:spf.bmv.jp ~all"
Technical Files
Robots
Sitemap
Cloudflare Radar
Provider Health
ai.provider
traffic.provider
Performance Metrics
0ms
Browser
6ms
Fetch
0ms
AI
6ms
Total
HTML Source Info
Keep exploring
Keep exploring from this report
Good pSEO pages should not strand the visitor. These links keep the journey moving through adjacent directories and comparable live reports.