cursor.com
Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.
Run a live full scan of cursor.com
On-demand: ports, banners, TLS, tech-stack, subdomains and origin/IP-leak detection. Results are shared publicly for everyone to link to.
DNS Records
WHOIS / Registration
Registration data planned
Registrar, creation/expiry dates and domain status via RDAP. Rolling out gradually — bulk WHOIS is rate-limited, so we resolve on a prioritized cadence.
Subdomains
Every subdomain we know about — harvested from CT-log SANs, scan-observed certs and HTML body references — paired with its current A/AAAA target.
| Subdomain | Resolves to | Last seen |
|---|---|---|
| origin.cursor.com | 2026-06-23 18:07:47.027 | |
| www.cursor.com | 2026-07-27 20:43:03.212 | |
| review.cursor.com | 2026-06-22 04:16:31.791 | |
| docs.cursor.com | 2026-07-23 20:30:23.856 | |
| downloads.cursor.com | 2026-06-18 08:32:34.679 | |
| forum.cursor.com | 2026-05-27 00:08:10.042 | |
| review.stg.cursor.com | 2026-06-20 08:35:10.022 | |
| api.cursor.com | 2026-05-26 10:27:10.433 | |
| cluster-controller.internal.cursor.com | 2026-06-23 22:52:33.689 | |
| origin-staging.cursor.com | 2026-05-27 17:49:03.731 | |
| ss-gtm.cursor.com | 2026-06-20 01:11:46.306 | |
| cursor.com | 2026-07-28 19:02:52.609 | |
| downloads-290bb7e2.cursor.com | 1970-01-01 00:00:00.000 | |
| forum-ca97698b16aa.cursor.com | 1970-01-01 00:00:00.000 | |
| gitlabprivatelinktest-4b6b9287.cursor.com | 1970-01-01 00:00:00.000 | |
| status.cursor.com | 1970-01-01 00:00:00.000 |
Tech Stack
Tech detection pending
Wappalyzer-rules detect CMS, frameworks, analytics, JS libs and server-side languages on this domain.
TLS Certificates
Certificate observations pending
TLS certs naming this domain in subject or SANs will appear here as our scan-layer catches them.
IPs Citing This Domain
Hosts whose HTML body references this domain. Strong signal for origin/mirror/embed discovery.
Origin / IP-Leak
When a hostname is served behind a CDN (e.g. Cloudflare), the origin server can sometimes be identified by matching its TLS cert against the protected hostname. Findings shown here are heuristic candidates, not guarantees.
No origin-IP leaks detected (yet)
Either this domain doesn't sit behind a CDN, or we haven't seen a TLS cert from a non-CDN IP matching this hostname. Run a fullscan to refresh the cert→IP cross-reference.
Threat Intelligence
Domain threat-intel pending
Matches in URLhaus, OpenPhish, PhishTank, malware feeds, and Spamhaus DBL.
History
Domain timeline pending
Passive-DNS history accumulates as our forward-DNS crawler observes A/AAAA/MX/NS/TXT records over time.