No CMS or framework detected, hosted on Cloudflare.
Confidence reflects how many independent signals matched.
| Technology | Version | Confidence | First seen |
|---|---|---|---|
| Frontend Build Tools & CSS2 | |||
| – | Medium | 14 Oct 2026 | |
| – | Medium | 14 Oct 2026 | |
| CDN & Hosting1 | |||
| – | High | 14 Oct 2026 | |
| Transactional Email2 | |||
| – | High | 14 Oct 2026 | |
| – | High | 14 Oct 2026 | |
| Fonts & Icon Fonts1 | |||
| – | Low | 14 Oct 2026 | |
| Security, WAF & Bot Protection1 | |||
| – | High | 14 Oct 2026 | |
route3.mx.cloudflare.netroute2.mx.cloudflare.netroute1.mx.cloudflare.netsusan.ns.cloudflare.commitchell.ns.cloudflare.comv=spf1 include:_spf.mx.cloudflare.net ~allgoogle-site-verification=OsG8beyk7oFf6SI_cNPnKLaTrYH4XDO4UDZDzzbyLfUv=DMARC1; p=none; rua=mailto:support@heysquint.com# heysquint.com # # Everything here is public marketing copy and three legal documents. There is nothing to hide # from a crawler and nothing expensive to crawl, so this file exists to do two things: point at # the sitemap, and be a real text file — until 2026-08-23 this path returned the React home page # with a 200, because the server fell every unknown path back to `index.html`. # # **`/authorize` and `/connect` are deliberately NOT disallowed here.** They are credential # hand-off steps and must stay out of an index, but a `Disallow` is the wrong instrument for # that: it stops a crawler *fetching* the page, which means it never sees the `noindex` that # would drop it, and a URL that is linked from anywhere can still be indexed on the strength of # the link alone. So they are crawlable and answer with `X-Robots-Tag: noindex` — see # `static_site` in `web/server/src/main.rs`, which sends it from the same route list that # decides what is a 404. User-agent: * Allow: / Sitemap: https://heysquint.com/sitemap.xml