New: The State of Indie Launches: July 2026. The framework layer is the same everywhere. The payment layer is not. Read

← Back to browse

Waraki Music Player

Waraki Music Player

New Zealand Estimated origin: New Zealand

Added August 12, 2026 · Last analysed August 12, 2026 · via Hacker News

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 12 August 2026; the live site may have changed since.

Waraki Music Player 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 August 11, 2026. The site is hosted on DigitalOcean in the United States. The crawl picked up 3 technologies on this site, covering DNS providers, os, and servers. The stack includes 1st Domains DNS, Apache, and Ubuntu.

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

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 (3)

Infrastructure
DNS 1st Domains DNS
OS Ubuntu
Server Apache

Infrastructure

DNS
1st Domains DNS
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 27 Jul 2026 to 25 Oct 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
Favicon present
- Open Graph tags (title, image, description)
- Responsive viewport meta tag
- Canonical URL declared
- Twitter card meta tags
- Semantic HTML (nav, main, article)

Performance How?

676 ms Server response
21% Faster than peers
2016 ms Largest contentful paint
0.33 Cumulative layout shift
1.1 MB Page weight
958 KB Image weight
0 Console errors
0 Failed requests

3 images: 1 oversized, 3 without width/height, 3 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
? No directive declared
? None advertised

Well-Known Files

robots.txt
sitemap.xml
security.txt
llms.txt
ads.txt
humans.txt
? Privacy Policy not detected
? Terms of Service not detected
Detection works best on English language sites.

Security Headers (0/6)

Permissions-Policy experimental (check browser support)
X-XSS-Protection deprecated (use Content-Security-Policy)

Build

0 JS files
1 CSS files
0 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.