← Back to browse

Wado-lang

Write and run Wado in the browser: the compiler, the language server, and your program all execute client-side as WebAssembly.

Developer Tools

Added July 18, 2026 · Last analysed July 18, 2026 · via Hacker News · 57% unique tagline

Own this Launch?
Screenshot of Wado-lang

StackScope is a free public catalogue of indie launches. We find launches on Product Hunt, Hacker News and similar feeds, then crawl each site to detect its tech stack and score it for launch readiness: DNS, security headers, SEO basics. This page is what we saw on 18 July 2026; the live site may have changed since.

Wado-lang still has work before launch. Main gaps: missing several security headers, incomplete legal pages, and no robots.txt or sitemap.

Launched on Hacker News on July 17, 2026. The site is hosted on GitHub Pages and served through Fastly. The crawl picked up 6 technologies on this site, covering analytics, CDN, DNS providers, and hosting. The stack includes AWS Route 53, Fastly, and GitHub Pages.

For context, it's on one of the most common stacks we track, shared by 1,743 launches.

If you own this site, refresh the snapshot and see the full fix list any time →

3.0
StackScope Score
Poor
64/100 Launch Readiness
Well prepared
0/6 Security Headers
Poor
2/3 Legal
Partial
0/2 Crawl files
Missing
85/100 Performance
Fast
Vibe Score 0 · No AI signals
How much the site looks AI-generated. Informational pattern-match signal, not a verdict. Does not feed the StackScope Score. See which fingerprints fired →

Tech Stack (6)

Infrastructure
CDN Fastly
DNS AWS Route 53
Hosting GitHub Pages
Build & Framework
JavaScript library Monaco Editor
Analytics & Marketing
Analytics Google Analytics (3)
Tag management Google Tag Manager medium

Infrastructure

Network
FASTLY - Fastly, Inc., US
AS54113 · US
DNS
AWS Route 53
Authoritative nameserver
DNSSEC
Not enabled
DNS responses unsigned. Cache-poisoning vulnerable.
Green hosting
Not green hosted
No green-energy record. Data from The Green Web Foundation.
SSL Certificate
Let's Encrypt
Valid 29 Jun 2026 to 27 Sep 2026
Certificate as captured in this snapshot, not a live check.

Email Security

✗
SPF Not published. Your domain can be spoofed in phishing emails.
?
DKIM Not detected at common selectors. Your provider may use a custom one.
✗
DMARC Not published. Receivers fall back to permissive defaults.
?
MTA-STS Not deployed. Mail to your domain can be downgraded to plaintext en route.
?
TLS-RPT Not configured. You won't hear about silent SMTP TLS handshake failures.

Storage (0)

This site uses no client-side storage we could detect on page load.

Readiness Breakdown How?

✓ Custom title and meta description
✓ Responsive viewport meta tag
✓ Favicon present
✓ Semantic HTML (nav, main, article)
- Open Graph tags (title, image, description)
- Canonical URL declared
- Twitter card meta tags

Performance How?

140 ms Server response
84% Faster than peers
432 ms Largest contentful paint
0.00 Cumulative layout shift
3.7 MB Page weight
37 KB Image weight
1 Third-party domains
0 Console errors
0 Failed requests

⚠ 1 images: 1 oversized, 1 without width/height, 1 missing alt text

Indicative grade from a single automated render, not a substitute for Lighthouse or field data, and not part of the StackScope score.

AI Stance

No AI stance declared
✗ llms.txt published
✓ No AI bots blocked in robots.txt
Content-Signal
? No directive declared
Link headers
? None advertised

Well-Known Files

✗ robots.txt
✗ sitemap.xml
✗ security.txt
✗ llms.txt
✗ ads.txt
✗ humans.txt

Legal

✓ Privacy Policy
/privacy.html
? Terms of Service not detected
? Analytics present, but it set no tracking cookies on our visit (it may be opt-in-gated).

Security Headers (0/6)

✗
Referrer-Policy
✗
X-Frame-Options
✗
Permissions-Policy experimental (check browser support)
✗
X-Content-Type-Options
✗
Content-Security-Policy
✗
Strict-Transport-Security
–
X-XSS-Protection deprecated (use Content-Security-Policy)

Build

3 JS files
1 CSS files
1 Third-party domains

Brand Colours

Something not look right? If a technology shown here is wrong or out of date, email [email protected] and we'll review it.