Check-Host.cc

Domain

help.bing.microsoft.com

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

Run a live full scan of help.bing.microsoft.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
11
A/AAAA targets
Subdomains
CT + scan + body
Record Types
2
seen in DNS
Observed Certs
12
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

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.

47.83.28.132:443 href · ×3
8.210.40.15:80 href · ×2
178.253.32.155:443 href · ×2
129.154.57.92:443 href · ×2
192.129.200.200:80 href · ×2
146.56.147.111:443 href · ×2
79.76.120.45:80 href · ×2
64.118.130.24:443 href · ×2
154.17.229.71:443 href · ×2
46.38.253.172:80 href · ×2
170.9.27.4:80 href · ×2
67.230.176.36:443 href · ×2
77.93.157.143:443 href · ×2
168.138.191.244:8080 href · ×2
150.230.61.134:80 href · ×1
155.248.163.194:80 href · ×1
65.49.195.189:80 href · ×1
23.88.96.149:80 href · ×1
95.181.190.114:80 href · ×1
176.122.185.50:80 href · ×1
45.66.216.166:80 href · ×1
14.137.244.117:80 href · ×1
45.62.117.165:80 href · ×1
65.108.253.67: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.