www.crunchyroll.com
“Anime News, Top Stories & In-Depth Anime Insights - Crunchyroll News”
Tech check
What the site says about itself, next to what its public page actually loads. Facts only, no verdict: you decide.
The page doesn't make tech claims we check for (AI, on-chain, wallets, trading, own chain, staking, live data, an app).
What it is
- The Internet Archive first saved this site on 2006-07-15 (7415 days ago).E65
- The site describes itself as: “Stay on top of anime news and updates straight out of Japan with Crunchyroll News. From breaking stories to evergreen content, get all your ”E2
- It's built with React and Next.js (common tools for building web apps).E15E16
- In your browser it saves small bits of data in your browser.E22
- It has sections such as /privacy, /news, /authorize, /profile, /auth/v1/token and /accounts/v1/me.E45E46
- While loading, it called 2 endpoints on its own servers, such as /i18n/cxweb/en_US.json and /auth/v1/token.E24E25
Where your data goes
Analytics & trackingCount visits and record what you do on the page. 1
| cdn.segment.com | Segment: customer-data pipeline that forwards events to other tools | 4×E7 |
Consent & bot protectionCookie banners, CAPTCHAs and bot checks. 2
| cdn.cookielaw.org | OneTrust: cookie consent banner | 10×E8 |
| geolocation.onetrust.com | OneTrust: cookie consent banner | 1×E9 |
FontsDownload typefaces. 1
| fonts.googleapis.com | Google Fonts: fonts | 1×E5 |
How key features work
Sign-in and accounts
Sign-in and account features show up in its code or traffic (/auth/v1/token, /accounts/v1/me, /subs/v1/subscriptions/{externalAccountId}/benefits and /accounts/v1/email_verification).E25E26E28
/auth/v1/token/accounts/v1/me/subs/v1/subscriptions/{externalAccountId}/benefits/accounts/v1/email_verificationLoading its content
Its content loads from its own API while you browse (/i18n/cxweb/en_US.json and /auth/v1/token).E24E25
/i18n/cxweb/en_US.json/auth/v1/tokenSearch
Search runs through /search-categories and /stories/search.E32E36
/search-categories/stories/searchMeasuring what you do
Visits and clicks are measured with Segment, Google tag (gtag.js) and Meta Pixel (found in its traffic or its code).E7E17E18E19
SegmentGoogle tag (gtag.js)Meta PixelSaving data on your device
It saves data in your browser (localStorage), so some things persist between visits.E22
local_storageCookies and storage
Names only. We never store the values.
Pages and API calls
Pages it links to
/privacy/news/authorize/profile/auth/v1/token/accounts/v1/me/accounts/v1/me/profile/accounts/v1/usernames/accounts/v1/me/notification_settings/accounts/v1/me/credentials/accounts/v1/email_verification/accounts/v1/phone/set_email/content/v2/cms/objects/{contentIds}/content/v2/discover/similar_to/{guid}/subs/v1/subscriptions/{externalAccountId}/benefits/subs/v1/subscriptions/{externalAccountId}/eligibility/cr_premium.1_month/subs/v2/products/{sku}/subs/v3/subscriptions/{externalAccountId}/stories/stories/search/search-categories/widget/{name}/Endpoints
Called while loading (seen) or named in the code (code).
| static.crunchyroll.com/i18n/cxweb/en_US.json | seenE24 |
| www.crunchyroll.com/auth/v1/token | seenE25 |
| /accounts/v1/me | codeE26 |
| /content/v2/discover/similar_to/{guid} | codeE27 |
| /subs/v1/subscriptions/{externalAccountId}/benefits | codeE28 |
| /stories | codeE29 |
| /widget/{name} | codeE30 |
| /accounts/v1/email_verification | codeE31 |
| /search-categories | codeE32 |
| /content/v2/cms/objects/{contentIds} | codeE33 |
| /accounts/v1/me/credentials | codeE34 |
| /accounts/v1/me/profile | codeE35 |
| /stories/search | codeE36 |
| /accounts/v1/usernames | codeE37 |
| /subs/v3/subscriptions/{externalAccountId} | codeE38 |
| /accounts/v1/phone/set_email | codeE39 |
| /accounts/v1/me/notification_settings | codeE40 |
| /subs/v2/products/{sku} | codeE41 |
| /subs/v1/subscriptions/{externalAccountId}/eligibility/cr_premium.1_month | codeE42 |
| /auth/v1/token | codeE43 |
| /api/v2 | codeE44 |
Evidence
Every sentence above points to one of these. Code references show the file, line:column and the short identifier that matched, never the site's code itself.
Limits
- We only see what your browser sees: code and requests on a first visit, without logging in or accepting cookie banners. What the servers do with data is invisible from outside.
- Site code is usually minified (compressed), so names are partly lost and some code may be only partly analysed.
- Some trackers only load after you accept cookies or log in, so the real list can be longer.
- We visited from a server in the United States. Sites load different trackers and cookie banners in different countries (visitors in the EU usually get a consent banner first).
- This text was written from fixed templates because no AI writer was available. It uses exactly the same evidence.
- The code reader hit its size budget on parts of 8 large bundle file(s); those parts weren't fully analysed.
Facts, not judgements: this page describes what the code and traffic show, not anyone's intent. Not financial advice. Case id J45hAMcr.