Considering it.
Backend is Go on a single-node K8s-"Cluster".
Frontend is vanilla JS on the same Hetzner-Box.
Code-situation in the midst of this ongoing "HN-Feuertaufe" is a bit … well.
What would make it useful for you - self-hosting capability, or contributing to detection logic?
EDIT 2 (48h later — shipped based on your feedback after a rough and a good night of sleep):
Should be fixed:
- Hybrid Geoip + ASN detection (no more nsa.gov/google.com false positives)
- AWS, Azure, Google Cloud, Cloudflare, DigitalOcean, Vercel, Netlify detection
- Links vs embeds — href to Twitter ≠ dependency on Twitter
- Lazy-loaded YouTube/Vimeo (lite-youtube facades)
- Adequacy tier scoring — UK, Switzerland, Japan get -15 (trusted, not sovereign) instead of 0
- Unquoted iframe detection (LinkedIn embeds)
gov.cn no longer scores 100%. admin.ch no longer scores 100%. The "sovereignty" label now hopefully means something.
Still open:
- DNS/registrar checks (v2)
- One reported LetsEncrypt cert error (can't reproduce)
Details on Vercel:
I try to detect via response headers (x-vercel-id), so custom domains are hopefully flagged correctly. Cloudflare for DNS is intentionally not pennalized — it's a proxy layer, not hosting (that was also stated in the methodology-popup from the beginning). I try that the origin server determines your hosting score.
Thanks to everyone who took the time. We (meaning all of you, who tested, tried and commented and maybe I, myself) made this tool hopefully significantly better.
And to have it stated here too: Though it might sound ironic or something (especially via a board like this): I and my partner never meant to insult anybody. We have profound respect for quality engineering outside of our borders. It even inspires us.
Update on the Cloudflare point: I now detect Vercel and Netlify hosting via response headers (catches custom domains). Cloudflare as CDN/DNS proxy is intentionally not flagged as US hosting — the origin server behind it could be EU. This is documented in the methodology popup.
The other issues you raised (social links vs embeds, US-hosted sites not detected) were fixed in earlier updates.
true. some socialmedia was too aggressive - should be resolved.
for yt: i tried to fix the lazy-loaded YouTube detection. Tool now catches:
- iframes with data-src
- web components: <lite-youtube>, <lite-youtube-embed>, <youtube-video>, <lite-vimeo>, <lite-vimeo-embed>, <vimeo-video>
One thing I stumbled over: if YT-URL only lives inside a JS variable and gets injected on click with no trace in the HTML. That's a static analysis limitation.
And:
React facades that load a YouTube thumbnail → already detected. React facades that use a local/self-hosted placeholder image with only a video ID in a data attribute → not detected.
You mind sharing a URL so I can verify it works against your site?
I know some sites serve incomplete cert chains (missing the intermediate). Browsers fix this automatically, Go doesn't. have your tested a site with broken cert chain? got a url to share? Would help me pin down the issue.
*GeoIP* - The ASN-only approach was too restrictive (I tested mostly with orf.at and such). Now using oschwald/geoip2-golang with DB-IP Lite. Hybrid detection: ASN for known providers, GeoIP fallback for everything else.
kapsi.fi now correctly shows as EU/Finland (was the false positive many caught). google.com: 54% (US detected), reddit.com: 94% (Canada - has EU adequacy decision). Added all EU adequacy countries (UK, Switzerland, Japan, Canada, etc.) - no penalty, but labeled "Adequate" not "EU". Im not sure on this one. Im sure we'd like to get UK back in the Union so we get to see the Rolling Stones more often.
*Embeds* - A link TO twitter.com is no longer flagged as a dependency. Only actual embeds (script src, iframes) count now. This might also fix the "links to GitHub flagged as GitHub Pages hosting" issue - same root.
*Costs* - Reduced. Google Fonts swap is now €50-150, not €400-800. Costs were too enterprisy, now for small sites like ours :)
Need to feed some cows now.
Will iterate further when back.
PS: Please dont roast the latin. Its been a while.
1. Link to X profile ≠ dependency on X. Will differentiate links from embeds in v0.2.
2. Registrar check is a good thinking. Already have some stubs in the codebase. Namecheap is US and could theoretically be compelled. Adding to roadmap.
Thanks for the Bugs Bunny.
I'm detecting a LINK to GitHub Pages and marking it as hosting. That's wrong - hosting should only flag when the actual page is served from there.
Re fonts: "self-hosted" means fonts served from your domain (vs Google Fonts CDN). If you're using system fonts, that's a detection error on my end.
The reals:
1. Hosting detection: I'm matching links TO GitHub as hosting ON GitHub. That's wrong. Fix incoming.
2. US-hosted sites getting 100%: My ASN lookup isn't catching everything. I opted against GeoIP services (privacy reasons), but clearly the ASN-only approach has to much gaps.
3. Social links vs embeds: You're right. A link to Twitter isn't a dependency. An embed is. Will differentiate.
4. gov.uk/gov.cn perfect scores: The tool checks infrastructure, not jurisdiction. gov.uk probably serves from EU edge nodes. That said, the name. Also tried to mention this in the Methodology-Modal. But iterating on all legalese and features same time as a single dev did not land well with my sleeping patterns for v0.1. Will fix that too.
"EU sovereignty" is misleading for non-EU countries - point taken. Will think about better framings.
First: You are legends. Thanks for the massive roasting. Had a Haupt-Mieterversammlung directly after clicking "Submit" and was too tired (and scared) to directly address the issues afterwards. Reading your comments really delivers some intense cringe-moments over here seeing my bugs exposed. I try to frame it as some of the best feedback from some of the best engineers in the world. This helps (it does).
The core stuff: I chose to implement ASN-list lookups instead of a GeoIP service (to have less deps). Worked for my european test cases. Clearly not battle-tested enough for the wild.
What I'm hearing:
- Hosting detection has false positives (detecting links as hosting) and false negatives (US-hosted sites scoring 100%)
- Social media LINKS shouldn't count same as EMBEDS (fair point)
- Missing: registrar, TLD jurisdiction, DNS location
- AWS/Cloudflare detection is spotty
- Migration cost estimates are too high for small sites
- Some UI bugs on Firefox
What we shipped overnight (yes, while this was trending):
- "Hotfix" for our scanning friends over nsa.gov
What we ship from now on:
- Fix the real bugs
What would make it useful for you - self-hosting capability, or contributing to detection logic?
I am considering a api but need stability first.