Skip to content

Hostname

windsormazda.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:146
Registrant organisation
chris siefker
Contact emails
chris@siefker.com

Subdomains

Subdomain
pbx.windsormazda.com
www.windsormazda.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

Sample outbound links

Mail and authentication

Nameservers

  • ns1166.dns.dyn.com
  • ns2198.dns.dyn.com
  • ns3147.dns.dyn.com
  • ns4140.dns.dyn.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
  • ns1.mydyndns.org

MX records

  • windsormazda-com.mail.protection.outlook.com

SPF policy

  • include: spf.protection.outlook.com
  • include: barracuda.sellwindsor.com
  • include: da.sellwindsor.com

Threat-feed evidence

History

Related pages

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