← Back to browse

NanoDM

Automatically Send Instagram DMs From Comments & Replies

nanodm.com · Added June 20, 2026 · Last analysed June 20, 2026 · via · 43% 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 20 June 2026; the live site may have changed since.

NanoDM is partway there, with complete legal pages and clean crawl signals. Main gaps: missing several security headers and no email security records.

Launched on Product Hunt on June 20, 2026. The site is hosted on Amazon.com in the United States, with a domain registered 12 weeks before launch. The crawl picked up 9 technologies on this site, covering APIs, auth, CDN, and chat widgets. The stack includes Google Sign-In, Amazon Web Services, and AWS CloudFront.

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

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

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

Tech Stack (9) · Scale-up stack

Infrastructure
CDN AWS CloudFront
Cloud Amazon Web Services
DNS AWS Route 53
Hosting AWS S3
Build & Framework
API Wikimedia
Auth Google Sign-In
Developer tools Vite
Commerce & Payments
Payments Razorpay (5)
Business Tools
Chat Collect.chat (2)

Infrastructure

Network
AS16509 · US
DNS
AWS Route 53
Authoritative nameserver
DNSSEC
Not enabled
DNS responses unsigned. Cache-poisoning vulnerable.
SSL Certificate
Amazon
Valid 31 Mar 2026 to 14 Oct 2026
Certificate as captured in this snapshot, not a live check.
Domain Age
2 months
Registered Mar 2026 · Amazon Registrar, 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 (6)

Cookies (3)
NameLifetimeDetected as
collect_chat_page_load 29d Collect.chat
rzp_unified_session_id < 1h Razorpay
WMF-Uniq 12mo Wikimedia
Local storage (2)
KeySizeDetected as
rzp_checkout_anon_id 32 B Razorpay
rzp_device_id 65 B Razorpay
Session storage (1)
KeySizeDetected as
__rzp_risk 2.4 KB Razorpay

Readiness Breakdown How?

Custom title and meta description (partial) missing 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?

453 ms Server response
41% Faster than peers
1984 ms Largest contentful paint
0.00 Cumulative layout shift
3.1 MB Page weight
422 KB Image weight
8 Third-party domains
0 Console errors
0 Failed requests

20 images: 20 oversized, 20 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 copy signals +5
AI palette signals +5
AI layout signals +5

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

sitemap.xml (1 URLs)
security.txt
llms.txt
ads.txt
humans.txt
94% unique

Security Headers (0/6)

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

Build

Code splitting
6 JS files
1 CSS files
8 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.