Skip to content

Hostname

wbko.com

Last fetched

wbko.com resolves to 15.197.130.216, announced in 15.197.128.0/20 by AMAZON-02 - Amazon.com, Inc. in CA. wbko.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 · wbko.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/wbko.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:3786
Registrant organisation
******** ******** (see notes section below on how to view unmasked data)
Contact emails
********@*****.***, 294071@brandsightprivacy.com, dspofford@valleynewslive.com, dnsadmin@gray.tv

Subdomains

Subdomain
autodiscover.wbko.com
enps.wbko.com
qr.wbko.com
qrpage.wbko.com
remote.wbko.com
wn.wbko.com
ww2.wbko.com
www.wbko.com

Showing 8 of 8 subdomains (8 per page).

Web-graph footprint

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

Sample inbound links

Mail and authentication

Nameservers

  • ns01.gcd-dns.com
  • ns02.gcd-dns.com
  • 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

MX records

  • mxa-009d5501.gslb.pphosted.com
  • mxb-009d5501.gslb.pphosted.com

SPF policy

  • ip: 208.86.168.7/32
  • include: spf.us1.defend.egress.com
  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

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