Skip to content

Hostname

bbcnbank.com

Last fetched

bbcnbank.com resolves to 192.157.56.140, announced in 192.157.56.0/22 by SERVER-MANIA - B2 Net Solutions Inc. in US. bbcnbank.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 · bbcnbank.comRouting diversity3.0/10Peering density3.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/bbcnbank.com

Resolution chain

IPv6 resolution

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

Attribution

b2 net

ORIGIN_AS

WHOIS identity

Registrar
iana:472
Registrant organisation
alex choi
Contact emails
04aeb2230a28fd0a694035599f3acb6c@domaindiscreet.com, 259e204d0a28fd0a36bf8f00567d5472@domaindiscreet.com, 428d531c0a28fd0a5d6372e679a6c861@domaindiscreet.com, 4cc5bd060a28fd0a4f820592b250bac2@domaindiscreet.com, 83546fa80a28fd0a64dbf9ac0d361ce1@domaindiscreet.com, a75d6ad70a28fd0a65cbb221d337a0d8@domaindiscreet.com, cf1575a50a28fd0a66d3b9c7a7ad2a14@domaindiscreet.com, alex.choi@bbcnbank.com, bbcnbank.com@superprivacyservice.com, domains@namemanagementgroup.com, e7f4e77f0a28fd0a1de6e6363fee0295@domaindiscreet.com, eb98bd030a28fd0a006309211242010b@domaindiscreet.com, sean.wang@bbcnbank.com, cary.yi@bbcnbank.com

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • ns1.brainydns.com
  • ns2.brainydns.com
  • ns1.dingodns.com
  • ns2.dingodns.com
  • ns1.emu-dns.com
  • ns2.emu-dns.com
  • ns1.kirklanddc.com
  • ns2.kirklanddc.com
  • ns1.koaladns.com
  • ns2.koaladns.com
  • ns1.magpiedns.com
  • ns2.magpiedns.com
  • ns1.milesmx.com
  • ns1.numbatdns.com
  • ns1.squirreldns.com

Threat-feed evidence

History

Related pages

Pivot from bbcnbank.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: "bbcnbank.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.