Check-Host.cc

Domain

segmentfault.com

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

Run a live full scan of segmentfault.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
8.152.202.66
AAAA
MX
10 hzmx02.mxmail.netease.com, 5 hzmx01.mxmail.netease.com
NS
ns3.dnsv3.com, ns4.dnsv3.com
TXT
MS=1DB32B475AC8829DFD0271BC986A4A44CB65CDA8, v=spf1 include:spf.163.com -all, verification-code-site-App_feishu=0fo2Fzmg9rNKrduJxNdm, verification-code-site-App_feishu=b3dyZq69cmo9duLi2JG4.
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

Subdomain enumeration pending

Every subdomain ever issued a TLS cert under this apex — extracted from Certificate Transparency logs, our own scan observations and body references.

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.

173.242.115.159:80 href · ×7
101.35.102.246:80 href · ×4
49.232.172.83:443 href · ×4
173.249.200.210:443 href · ×4
51.81.222.186:443 href · ×4
218.3.205.77:443 href · ×4
8.136.48.83:443 href · ×4
47.110.140.201:80 href · ×3
124.220.222.26:443 href · ×2
8.146.207.235:80 href · ×2
51.81.222.186:80 href · ×2
8.218.217.238:443 href · ×2
111.229.242.224:443 href · ×2
39.108.247.198:80 href · ×2
47.109.39.101:443 href · ×2
1.12.77.163:443 href · ×2
114.132.187.96:443 href · ×2
101.43.124.229:443 href · ×2
192.18.136.201:443 href · ×2
47.90.202.40:80 href · ×2
82.156.34.133:80 href · ×2
39.105.186.182:80 href · ×2
150.158.75.206:443 href · ×2
117.72.77.5:443 href · ×2
43.138.213.184:80 href · ×2
49.232.92.179:443 href · ×2
106.52.213.94:80 href · ×2
101.201.63.53:443 href · ×2
8.152.223.9:443 href · ×2
150.158.118.5:443 href · ×2
139.196.190.146:80 href · ×2
54.180.107.34:80 href · ×2
185.216.119.41:443 href · ×2
49.232.237.179:443 href · ×2
45.197.144.122:443 href · ×2
47.93.47.226:443 href · ×2
124.223.97.142:443 href · ×2
117.72.32.117:443 href · ×2
118.126.82.120:443 href · ×2
121.40.197.252:443 href · ×2
107.174.62.46:443 href · ×2
119.23.215.59:443 href · ×2
39.107.236.27:80 href · ×2
101.35.102.246:443 href · ×2
192.64.115.197:443 href · ×2
139.224.49.157:443 href · ×2
129.226.208.178:80 href · ×1
158.101.143.126:443 href · ×1
47.103.25.95:80 href · ×1
47.119.170.178: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.