Skip to content

Hostname

bgbjc.com

Last fetched

bgbjc.com resolves to 178.63.45.142, announced in 178.63.0.0/16 by HETZNER-AS - Hetzner Online GmbH in DE. bgbjc.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · bgbjc.comRouting diversity1.5/10Peering density8.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.2/10canon.whisper.security/host/bgbjc.com

Resolution chain

IPv6 resolution

No AAAA record for bgbjc.com is recorded in WhisperGraph.

Attribution

hetzner

ORIGIN_AS

WHOIS identity

Registrar
iana:269
Registrant organisation
chen an qi
Contact emails
3164866992@qq.com, lolose@126.com, proxy@whoisprotectservice.com, contact@whoissecure.net, 80bfc12a862e2dd12a8800955ae43bb807aaf805e95fa253ff2e224b45ae7be2@bgbjc.com.whoisproxy.org, 8b14df517ef0862b56725ce2372af5b06aa9906235fb00f6173503ab3ba3adaf@bgbjc.com.whoisproxy.org, 90f79489aae4c379b5cd77061704bf7ac4496c8f131158b2c40fbeddeba69dc8@bgbjc.com.whoisproxy.org, 9c4270554da587eb5cb36c265539a1cda106ce5c631646b8e55b69d2e3a4ee10@bgbjc.com.whoisproxy.org, e16350f78f15c5c837419b514a011d397d164be44cc7c56eee7338e124f61560@bgbjc.com.whoisproxy.org, f4daba86baa75c8ee54062bd7439e155759cbda7ee99aad43491e92c3be4ec9b@bgbjc.com.whoisproxy.org

Subdomains

Subdomain
m.bgbjc.com
pop.bgbjc.com

Showing 2 of 2 subdomains (2 per page).

Mail and authentication

Nameservers

  • ns1.nicns.net
  • ns2.nicns.net
  • ns3.nicns.net
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

Threat-feed evidence

History

Related pages

Pivot from bgbjc.com into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "bgbjc.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.