Skip to content

Hostname

stantonsace.com

Last fetched

stantonsace.com resolves to 199.96.124.1, announced in 199.96.124.0/24 by IMDC-AS12025 - Iron Mountain Data Center in US. stantonsace.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 · stantonsace.comRouting diversity1.5/10Peering density7.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/stantonsace.com

Resolution chain

Attribution

iron mountain center

ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of stantonsace.com owner
Contact emails
stantonsace.com-registrant@directnicwhoiscompliance.com, mike@carambat.com, 56ba99ac-d45a-4440-b1f2-769110ca4450@identity-protect.org, 6eddb82a-4aeb-4ee1-b346-b35cb7e5f38a@identity-protect.org, 85b04b13-b8ae-4c55-9ab0-c1b6db79ac9b@identity-protect.org, e1bed2b5-860f-4d27-aa05-d7179f7e8090@identity-protect.org, f2f4f145-82ce-4271-a057-5f6af91b9530@identity-protect.org

Subdomains

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.

Mail and authentication

Nameservers

  • ns-55.awsdns-06.com
  • ns-810.awsdns-37.net
  • 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
  • ns-1440.awsdns-52.org
  • ns-1750.awsdns-26.co.uk

MX records

  • mail.stantonsace.com

SPF policy

  • mx: stantonsace.com
  • include: sendsecuremail.net

Threat-feed evidence

History

Related pages

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