Skip to content

Hostname

wbls.com

Last fetched

wbls.com resolves to 192.0.66.22, announced in 192.0.97.0/24 by AUTOMATTIC - Automattic, Inc in US. wbls.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 · wbls.comRouting diversity1.5/10Peering density7.6/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/wbls.com

Resolution chain

IPv6 resolution

Attribution

automattic

ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
******** ******** (see notes section below on how to view unmasked data)
Contact emails
********@*****.***, admin@emmis.com, fred@wbls.com

Subdomains

Subdomain
dev.wbls.com
develop.wbls.com
micson.wbls.com
new.wbls.com
prd.wbls.com
preprod.wbls.com
sip.wbls.com
stg.wbls.com
vip.wbls.com
www.wbls.com

Showing 10 of 10 subdomains (10 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

Sample outbound links

Mail and authentication

Nameservers

  • denver.ns.cloudflare.com
  • vivienne.ns.cloudflare.com

MX records

  • wbls-com.mail.protection.outlook.com

SPF policy

  • ip: 171.159.0.0/16
  • ip: 171.161.0.0/16
  • include: spf.clearslide.com
  • include: eblastengine.com
  • a: smtp.emarketron.com
  • include: us._netblocks.mimecast.com
  • include: spf.protection.outlook.com
  • include: aspmx.sailthru.com
  • mx: wbls.com
  • include: servers.mcsv.net
  • ip: 192.64.76.201
  • ip: 192.64.76.202
  • ip: 192.64.76.203
  • ip: 65.211.179.21
  • ip: 65.211.179.22

Threat-feed evidence

History

Related pages

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