startpage.com
Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.
Run a live full scan of startpage.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 |
|---|---|---|
| proxy3.startpage.com | 2026-06-17 03:46:31.597 | |
| startpage.com | 2026-07-27 10:31:11.024 | |
| www.startpage.com | 2026-07-28 16:36:45.579 | |
| av.startpage.com | 2026-07-23 05:32:54.849 | |
| eu-proxy.startpage.com | 2026-06-17 03:46:31.597 | |
| proxy1.startpage.com | 2026-07-19 05:49:02.105 | |
| us-proxy.startpage.com | 2026-06-17 03:46:31.597 | |
| pwlookup.tmt.startpage.com | 2026-06-04 06:17:42.463 | |
| auth.stage.startpage.com | 1970-01-01 00:00:00.000 | |
| gclient.tmt.startpage.com | 1970-01-01 00:00:00.000 | |
| get.startpage.com | 1970-01-01 00:00:00.000 | |
| hct-qa.tmt.startpage.com | 1970-01-01 00:00:00.000 | |
| proxy.startpage.com | 2026-06-17 03:46:31.597 | |
| proxy2.startpage.com | 2026-06-17 03:46:31.597 | |
| proxy4.startpage.com | 2026-06-17 03:46:31.597 | |
| proxy5.startpage.com | 2026-06-17 03:46:31.597 | |
| trackerlist.tmt.startpage.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.