Skip to content

Hostname

wwcsupply.com

Last fetched

wwcsupply.com resolves to 172.66.40.85, announced in 172.66.40.0/21 by CLOUDFLARENET - Cloudflare, Inc. in CA. wwcsupply.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 · wwcsupply.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/wwcsupply.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of wwcsupply.com owner
Contact emails
39223e22-3980-4fcd-b67a-e4bcbbc92d35@identity-protect.org, 60d9857b-a8ab-4075-9e7c-8272f06a3399@identity-protect.org, 61ca8d0b-5165-4ba4-a674-56b0c9d9fd2b@identity-protect.org, b787ce86-823b-4233-b065-9e405cd6e944@identity-protect.org, e2a4b684-cd65-473c-9c5b-18b8aabf29d7@identity-protect.org, owner-1004346@wwcsupply.com.whoisprivacyservice.org

Subdomains

Subdomain
dev.wwcsupply.com
uat1.wwcsupply.com

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

  • ashley.ns.cloudflare.com
  • dave.ns.cloudflare.com

MX records

  • wwcsupply-com.mail.protection.outlook.com

SPF policy

  • ip: 64.235.144.0/20
  • ip: 209.222.80.0/21
  • ip: 74.112.65.118/32
  • ip: 208.85.54.223/32
  • ip: 208.85.54.226/32
  • ip: 74.112.64.38/32
  • ip: 74.112.64.47/32
  • include: spf.ess.barracudanetworks.com
  • include: spf.protection.outlook.com
  • include: spf.sendinblue.com
  • ip: 13.59.31.115
  • ip: 18.188.189.237
  • ip: 24.173.1.66
  • ip: 72.249.131.156

Threat-feed evidence

History

Related pages

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