whee.ls
Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.
Run a live full scan of whee.ls
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 |
|---|---|---|
| 0040b573-55b4-49dd-ab9c-51a8949b3089.whee.ls | 1970-01-01 00:00:00.000 | |
| app.whee.ls | 1970-01-01 00:00:00.000 | |
| email.whee.ls | 2026-06-17 18:20:40.292 | |
| m.whee.ls | 2026-06-23 09:56:29.314 | |
| mailer.whee.ls | 1970-01-01 00:00:00.000 | |
| marketing.whee.ls | 1970-01-01 00:00:00.000 | |
| qa.whee.ls | 1970-01-01 00:00:00.000 | |
| tmsedm.whee.ls | 2026-06-23 14:57:05.679 | |
| uat.whee.ls | 2026-06-15 15:40:34.902 | |
| v1.whee.ls | 1970-01-01 00:00:00.000 | |
| v2.whee.ls | 1970-01-01 00:00:00.000 | |
| www.demo.whee.ls | 1970-01-01 00:00:00.000 | |
| www.dev.whee.ls | 2026-06-18 12:30:12.110 | |
| www.exchange.whee.ls | 2026-07-20 01:31:52.254 | |
| www.gjdgotqhaulaway.whee.ls | 2026-06-23 05:50:41.176 | |
| www.mail.whee.ls | 2026-07-25 14:08:30.545 | |
| www.marketing.whee.ls | 2026-06-04 13:44:16.553 | |
| www.qa.whee.ls | 2026-06-18 06:54:06.198 |
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
No citing IPs found yet
As the world-sweep progresses, hosts referencing this domain in their HTML will surface here.
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.