linux.do
Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.
Run a live full scan of linux.do
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 |
|---|---|---|
| check.linux.do | 2026-06-16 16:21:09.234 | |
| connect.linux.do | 2026-07-22 14:15:47.566 | |
| linux.do | 2026-07-28 17:13:52.071 | |
| nav.linux.do | 2026-07-22 14:15:47.566 | |
| pow.linux.do | 2026-06-24 02:56:20.780 | |
| ads.linux.do | 1970-01-01 00:00:00.000 | |
| autodiscover.linux.do | 1970-01-01 00:00:00.000 | |
| cdk.linux.do | 1970-01-01 00:00:00.000 | |
| docker-gcr.linux.do | 1970-01-01 00:00:00.000 | |
| docker-ghcr.linux.do | 1970-01-01 00:00:00.000 | |
| docker-hub.linux.do | 1970-01-01 00:00:00.000 | |
| docker-ui.linux.do | 1970-01-01 00:00:00.000 | |
| lottery.linux.do | 1970-01-01 00:00:00.000 | |
| mta-sts.linux.do | 1970-01-01 00:00:00.000 | |
| rate.linux.do | 1970-01-01 00:00:00.000 | |
| uptime.linux.do | 1970-01-01 00:00:00.000 | |
| webmail.linux.do | 1970-01-01 00:00:00.000 | |
| wiki.linux.do | 1970-01-01 00:00:00.000 | |
| www.linux.do | 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
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.