Check-Host.cc

Domain

would.do

Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.

Run a live full scan of would.do

On-demand: ports, banners, TLS, tech-stack, subdomains and origin/IP-leak detection. Results are shared publicly for everyone to link to.

Deep-scan now
Hosting IPs
2
A/AAAA targets
Subdomains
56
CT + scan + body
Record Types
seen in DNS
Observed Certs
2
in our scans

DNS Records

A
AAAA
MX
NS
TXT
CNAME
CAA

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
anything.would.do 2026-06-16 11:00:30.816
8.i.would.do
1970-01-01 00:00:00.000
abby.would.do
1970-01-01 00:00:00.000
all.would.do 2026-06-06 04:28:09.527
and.would.do
1970-01-01 00:00:00.000
ass.would.do 2026-06-23 21:44:46.881
bedroom.would.do
1970-01-01 00:00:00.000
cholild.would.do
1970-01-01 00:00:00.000
dealership.would.do
1970-01-01 00:00:00.000
europe.would.do
1970-01-01 00:00:00.000
evil.would.do
1970-01-01 00:00:00.000
foto.would.do 2026-07-27 22:28:57.726
fuck.would.do
1970-01-01 00:00:00.000
go.would.do
1970-01-01 00:00:00.000
human.would.do
1970-01-01 00:00:00.000
infrastructure.would.do 2026-06-03 00:01:16.132
kiddos.would.do
1970-01-01 00:00:00.000
kne.would.do 2026-07-24 06:54:07.813
knkw.would.do
1970-01-01 00:00:00.000
lad.would.do 2026-07-23 11:38:01.998
lusca.would.do
1970-01-01 00:00:00.000
m.would.do
1970-01-01 00:00:00.000
mindi.would.do
1970-01-01 00:00:00.000
mum.would.do 2026-06-16 13:18:19.067
nick.would.do
1970-01-01 00:00:00.000
no.kne.would.do 2026-07-24 06:45:51.066
noodle.would.do
1970-01-01 00:00:00.000
ok.would.do
1970-01-01 00:00:00.000
old.abby.would.do
1970-01-01 00:00:00.000
or.would.do
1970-01-01 00:00:00.000
ppl.would.do 2026-06-03 11:42:33.754
rua.would.do
1970-01-01 00:00:00.000
said.he.would.do
1970-01-01 00:00:00.000
show.would.do
1970-01-01 00:00:00.000
somebody.would.do
1970-01-01 00:00:00.000
somwone.would.do
1970-01-01 00:00:00.000
soup.would.do
1970-01-01 00:00:00.000
they.would.do
1970-01-01 00:00:00.000
things.i.would.do
1970-01-01 00:00:00.000
to.would.do 2026-07-22 01:50:43.878
trump.would.do
1970-01-01 00:00:00.000
weed.would.do
1970-01-01 00:00:00.000
why.you.would.do
1970-01-01 00:00:00.000
would.do
1970-01-01 00:00:00.000
www.19f49444-a522-4662-91c1-0aca3442f4e3.would.do 2026-07-17 23:26:49.957
www.dealership.would.do 2026-06-05 20:56:01.189
www.mom.would.do
1970-01-01 00:00:00.000
www.s.would.do
1970-01-01 00:00:00.000
www.said.would.do
1970-01-01 00:00:00.000
www.she.would.do
1970-01-01 00:00:00.000
www.zeke.would.do 2026-07-17 23:55:05.119
yes.i.would.do 2026-07-17 00:26:37.879

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

USP

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.