← Back to browse

墨卡 Moka

AI驱动的爆款文案排版工具

Added April 14, 2026 · Last analysed April 14, 2026 · via

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

墨卡 Moka is missing several launch fundamentals. What needs work: missing several security headers, incomplete legal pages, and no robots.txt or sitemap.

Launched on Product Hunt on April 14, 2026. The site is served through Cloudflare, with a domain registered in 2017. Our crawler found 5 technologies on this site, covering analytics, CDN, developer tools, and package cdn. The stack includes cdnjs, Cloudflare, and Cloudflare Web Analytics.

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

1.7
StackScope Score
Poor
61/100 Launch Readiness
Well prepared
0/3 Legal
Missing
0/2 Crawl files
Missing
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 (5)

Infrastructure
CDN Cloudflare (4)
Protocol HTTP/3 (2)
Build & Framework
Developer tools Vite
Package CDN cdnjs (2)
Analytics & Marketing
Analytics Cloudflare Web Analytics

Infrastructure

Network
AS13335 · US
DNSSEC
Not enabled
DNS responses unsigned. Cache-poisoning vulnerable.
SSL Certificate
Google Trust Services
Valid 25 Mar 2026 to 23 Jun 2026
Certificate as captured in this snapshot, not a live check.
Domain Age
8.6 years
Registered Dec 2017 · 阿里云计算有限公司

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.

Readiness Breakdown How?

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

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
? Analytics present, but it set no tracking cookies on our visit (it may be opt-in-gated).
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)

Performance

96ms response time
Faster than 95% of sites
2 third-party domains loaded

Build

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