wellsaidlabs.com
Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.
Run a live full scan of wellsaidlabs.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 |
|---|---|---|
| status.wellsaidlabs.com | 2026-07-21 08:32:12.525 | |
| vjs.wellsaidlabs.com | 2026-06-03 07:05:54.040 | |
| admin.wellsaidlabs.com | 1970-01-01 00:00:00.000 | |
| auth.staging.wellsaidlabs.com | 1970-01-01 00:00:00.000 | |
| auth.wellsaidlabs.com | 1970-01-01 00:00:00.000 | |
| developer.wellsaidlabs.com | 2026-07-25 01:46:29.625 | |
| docs.wellsaidlabs.com | 1970-01-01 00:00:00.000 | |
| loki.monitoring.wellsaidlabs.com | 2026-05-27 16:34:03.150 | |
| monitoring.wellsaidlabs.com | 1970-01-01 00:00:00.000 | |
| promtail.monitoring.wellsaidlabs.com | 1970-01-01 00:00:00.000 | |
| scim.wellsaidlabs.com | 2026-07-20 08:17:01.502 | |
| staging.tts.wellsaidlabs.com | 2026-06-16 05:28:52.196 | |
| staging.wellsaidlabs.com | 1970-01-01 00:00:00.000 | |
| studio.wellsaidlabs.com | 2026-06-18 19:36:16.867 | |
| tempo.monitoring.wellsaidlabs.com | 2026-06-22 16:45:51.707 | |
| trust.wellsaidlabs.com | 1970-01-01 00:00:00.000 | |
| tts.wellsaidlabs.com | 2026-06-20 06:50:34.738 | |
| wellsaidlabs.com | 2026-07-27 07:19:40.268 | |
| www.wellsaidlabs.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
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
Passive DNS — every value this name ever resolved to and when we first / last observed it. Updates every cycle of our forward-DNS crawler.
| Type | Value | First seen | Last seen |
|---|---|---|---|
| TXT | MS=ms20724718 | 2026-06-14 23:07:05.130 | 2026-07-27 07:19:40.268 |
| TXT | google-site-verification=tEel8uOm0bp25miBrnos5OguJdvJSpD4QJ1KCugLx08 | 2026-06-14 23:07:05.130 | 2026-07-27 07:19:40.268 |
| NS | dan.ns.cloudflare.com | 2026-06-14 23:07:05.130 | 2026-07-27 07:19:40.268 |
| MX | 5 alt2.aspmx.l.google.com | 2026-06-14 23:07:05.130 | 2026-07-27 07:19:40.268 |
| MX | 10 alt4.aspmx.l.google.com | 2026-06-14 23:07:05.130 | 2026-07-27 07:19:40.268 |
| MX | 1 aspmx.l.google.com | 2026-06-14 23:07:05.130 | 2026-07-27 07:19:40.268 |
| TXT | v=spf1 include:spf.mandrillapp.com include:_spf.google.com include:mail.zendesk.com include:amazonses.com include:6497605.spf03.hubspotemail.net ~all | 2026-06-14 23:07:05.130 | 2026-07-27 07:19:40.268 |
| MX | 5 alt1.aspmx.l.google.com | 2026-06-14 23:07:05.130 | 2026-07-27 07:19:40.268 |
| NS | amanda.ns.cloudflare.com | 2026-06-14 23:07:05.130 | 2026-07-27 07:19:40.268 |
| TXT | anthropic-domain-verification-9n1ghy=hPAD24yaYuJ7ODNlUmLNkWGJu | 2026-06-14 23:07:05.130 | 2026-07-27 07:19:40.268 |
| A | 198.202.211.1 | 2026-06-14 23:07:05.130 | 2026-07-27 07:19:40.268 |
| MX | 10 alt3.aspmx.l.google.com | 2026-06-14 23:07:05.130 | 2026-07-27 07:19:40.268 |