Check-Host.cc

Domain

bigesj.com

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

Run a live full scan of bigesj.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

A
106.13.24.22
AAAA
MX
NS
dns10.hichina.com, dns9.hichina.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
st.bigesj.com 2026-07-25 02:11:47.833
bigesj.com 2026-07-27 17:39:35.256
cdn.bigesj.com 2026-07-25 02:11:47.833
sse.bigesj.com
1970-01-01 00:00:00.000
tmp.bigesj.com
1970-01-01 00:00:00.000
www.sse.bigesj.com
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

Hosts whose HTML body references this domain. Strong signal for origin/mirror/embed discovery.

106.12.115.228:443 href · ×10
47.98.222.212:80 href · ×6
47.98.232.59:80 href · ×6
120.55.33.198:443 href · ×6
154.17.4.213:443 href · ×4
47.117.42.178:443 href · ×4
82.156.151.85:80 href · ×2
42.192.39.170:443 href · ×2
212.64.3.78:8080 href · ×2
182.61.13.130:443 href · ×1
47.97.47.11:80 href · ×1
106.12.115.228:443 og:url · ×1
81.68.236.161:443 href · ×1
106.12.115.228:443 canonical · ×1
38.190.210.123:443 href · ×1
47.114.6.14: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

Passive DNS — every value this name ever resolved to and when we first / last observed it. Updates every cycle of our forward-DNS crawler.

Type Value First seen Last seen
NS dns10.hichina.com 2026-05-26 08:28:45.083 2026-07-27 17:39:35.256
A 106.13.24.22 2026-05-26 08:28:45.083 2026-07-27 17:39:35.256
NS dns9.hichina.com 2026-05-26 08:28:45.083 2026-07-27 17:39:35.256