Domain

hitwebcounter.com

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

DNS Check HTTP Check Run Full Scan .com TLD

Run a live full scan of hitwebcounter.com

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

A/AAAA targets

Subdomains

CT + scan + body

Record Types

seen in DNS

Observed Certs

in our scans

DNS Records

104.21.69.153, 172.67.209.162

AAAA

2606:4700:3033::6815:4599, 2606:4700:3033::ac43:d1a2, 2606:4700:3037::6815:4599, 2606:4700:3037::ac43:d1a2, ::

—

kip.ns.cloudflare.com, lucy.ns.cloudflare.com

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
hitwebcounter.com	104.21.69.153 2606:4700:3037::6815:4599 2606:4700:3033::ac43:d1a2 172.67.209.162 +3	2026-07-28 13:32:41.076
www.hitwebcounter.com	172.67.209.162 2606:4700:3033::ac43:d1a2 2606:4700:3037::6815:4599 104.21.69.153 +2	2026-07-27 08:11:55.706

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.

124.221.213.242:80 href · ×3

37.143.175.18:80 href · ×2

76.137.25.32:443 href · ×2

103.211.202.246:80 href · ×2

114.130.119.106:443 href · ×2

77.104.145.156:80 href · ×2

144.16.144.72:80 href · ×2

13.127.254.238:80 href · ×2

216.115.203.12:443 href · ×2

144.16.144.237:443 href · ×2

175.126.176.31:80 href · ×2

93.90.202.137:80 href · ×2

45.76.1.189:80 href · ×2

51.81.35.142:443 href · ×2

60.251.135.142:80 href · ×2

193.212.194.10:443 href · ×2

114.34.46.102:443 href · ×2

144.16.144.72:443 href · ×2

92.27.175.232:80 href · ×2

140.120.32.208:80 href · ×1

212.24.107.204:80 href · ×1

36.50.18.84:80 href · ×1

64.234.200.144:80 href · ×1

59.125.197.4:80 href · ×1

110.159.249.72:80 href · ×1

150.136.36.9:80 href · ×1

110.159.230.73:80 href · ×1

139.99.130.155:443 href · ×1

198.204.242.13:80 href · ×1

164.52.196.134:8000 href · ×1

203.162.36.146:80 href · ×1

167.172.210.243:443 href · ×1

51.77.244.166:443 href · ×1

144.16.144.120:80 href · ×1

209.11.168.4:8080 href · ×1

87.62.99.17:443 href · ×1

185.243.215.145:443 href · ×1

213.232.115.96:80 href · ×1

18.139.162.169:443 href · ×1

144.16.144.76:443 href · ×1

185.243.215.145:80 href · ×1

217.154.229.238:80 href · ×1

104.211.93.88:80 href · ×1

178.172.235.35:443 href · ×1

195.228.251.233:80 href · ×1

186.50.153.20:80 href · ×1

162.243.186.152:443 href · ×1

79.96.207.47:80 href · ×1

164.100.141.140:443 href · ×1

217.104.17.22:443 href · ×1

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.