Domain

quge5.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 quge5.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

—

AAAA

—

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
quge5.com	139.45.197.114	2026-07-27 01:56:40.851

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.

43.162.99.141:443 href · ×2

155.94.173.199:443 href · ×2

213.165.95.182:443 href · ×2

162.35.163.45:80 href · ×2

43.162.107.212:443 href · ×2

52.45.52.51:443 href · ×2

141.148.233.75:443 href · ×2

104.168.94.133:443 href · ×1

51.222.135.173:80 href · ×1

159.203.79.120:443 href · ×1

139.84.168.82:443 href · ×1

160.153.191.128:443 href · ×1

43.162.89.211:443 href · ×1

43.162.107.135:443 href · ×1

45.192.111.155:443 href · ×1

94.130.37.172:443 href · ×1

5.189.176.135:443 href · ×1

43.162.107.3:443 href · ×1

43.162.101.6:443 href · ×1

165.227.152.93:443 href · ×1

104.249.19.10:80 href · ×1

74.208.35.131:443 href · ×1

43.162.114.46:443 href · ×1

45.55.76.27:443 href · ×1

43.162.94.38:443 href · ×1

43.162.88.45:443 href · ×1

47.74.38.230:80 href · ×1

43.128.57.55:443 href · ×1

43.162.103.111:443 href · ×1

62.84.177.8:443 href · ×1

43.162.119.3:443 href · ×1

43.162.101.10:443 href · ×1

146.190.42.36:443 href · ×1

43.162.106.28:443 href · ×1

43.162.90.96:443 href · ×1

43.162.84.24:443 href · ×1

201.182.96.148:443 href · ×1

43.162.118.50:443 href · ×1

43.162.107.90:443 href · ×1

43.162.87.68:443 href · ×1

43.162.86.74:443 href · ×1

111.90.158.245:443 href · ×1

43.162.97.115:443 href · ×1

43.162.122.239:443 href · ×1

43.162.104.197:443 href · ×1

43.133.87.13:80 href · ×1

199.247.6.47:443 href · ×1

43.162.105.8:443 href · ×1

5.189.160.75:443 href · ×1

43.162.126.38: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.