blackcalf.baby
“Black Calf | Coldest calf breathing”
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 has never saved this site, so it is probably new.E13
- The site describes itself as: “10% sent to ansemconzimp | Paired to $ANSEM 🐂🀄️”E2
- It's built with Next.js and React (common tools for building web apps).E8E9
- In your browser it can copy text to your clipboard.E10
- It has sections such as /ansem-callout.jpeg.E12
- While loading, it called 1 endpoint on its own servers, such as /api/holdings.E11
Where your data goes
On a first visit the page only talked to its own servers (blackcalf.baby).
How key features work
Loading its content
Its content loads from its own API while you browse (/api/holdings).E11
/api/holdingsCookies and storage
Names only. We never store the values.
Pages and API calls
Pages it links to
//ansem-callout.jpegEndpoints
Called while loading (seen) or named in the code (code).
| blackcalf.baby/api/holdings | seenE11 |
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 2 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 2PFbe3px.