Skip to content

Hostname

proxyaz.com

Last fetched

proxyaz.com resolves to 104.26.12.6, announced in 104.26.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. proxyaz.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 · proxyaz.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/proxyaz.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:2487
Registrant organisation
domain admin
Contact emails
owner@proxyaz.com.customers.whoisprivacycorp.com, pw-1f06615675161fb7d9648fa9a370364c@privacyguardian.org

Subdomains

Subdomain
cdn.proxyaz.com
files.proxyaz.com
myvps.proxyaz.com
payment.proxyaz.com
status.proxyaz.com
sub.proxyaz.com
support.proxyaz.com
www.proxyaz.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

Sample outbound links

Mail and authentication

Nameservers

  • lorna.ns.cloudflare.com
  • todd.ns.cloudflare.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

  • mx.yandex.net

SPF policy

  • include: amazonses.com
  • include: mxroute.com
  • include: _spf.yandex.net
  • include: mailgun.org

Threat-feed evidence

History

Related pages

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