← Back to browse

ccglass

See the full system prompt, tool schemas, message history, token/cache/cost in real time. One command: ccglass claude, ccglass codex.

ccglass.jianshuo.dev · Added June 17, 2026 · Last analysed June 17, 2026 · via · 62% unique tagline

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

ccglass is early-stage. What needs work: missing several security headers, incomplete legal pages, and no robots.txt or sitemap.

Launched on Product Hunt on June 16, 2026. The site is hosted on Cloudflare in the United States, with a domain registered 1 week before launch. We've detected 4 technologies on this site, covering analytics, CDN, web fonts, and protocol. The stack includes Cloudflare, Cloudflare Web Analytics, and Google Fonts.

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

Vibe Score 100 · Strong AI signals
Informational pattern-match signal. Does not feed the StackScope Score. See which fingerprints fired →

Tech Stack (4)

Infrastructure
CDN Cloudflare
Protocol HTTP/3
Build & Framework
Font Google Fonts
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 8 Jun 2026 to 6 Sep 2026
Certificate as captured in this snapshot, not a live check.
Domain Age
8 days
Registered Jun 2026 · CloudFlare, Inc.

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
Open Graph tags (title, image, description) (partial) missing og:image
Responsive viewport meta tag
Semantic HTML (nav, main, article)
Page title is 63 characters (advisory) Google only shows about 60 characters of the title in search results; aim for 50–60 to keep the whole thing visible.
- Canonical URL declared
- Twitter card meta tags
- Favicon present

Performance How?

133 ms Server response
85% Faster than peers
308 ms Largest contentful paint
0.00 Cumulative layout shift
714 KB Page weight
372 KB Image weight
3 Third-party domains
0 Console errors
0 Failed requests

1 images: 1 without width/height

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

Vibe Score Breakdown How?

SignalPoints
AI onboarding signals +5
AI writing signals +5
AI iconography signals +3
AI code-structure signals +5
AI scaffolding signals +8
Recognised AI builder signature +30
AI CSS signals +15

This score is based on structural patterns and is not definitive. Many legitimate sites may trigger signals, and AI-built sites may go undetected. It should be treated as an indicator, not a verdict.

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
? Consent manager not detected
Analytics detected; tracking fires without visitor opt-in.
Detection works best on English language sites.

Security Headers (2/6)

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

Build

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