Skip to content

Hostname

sandrevolution.com

Last fetched

sandrevolution.com resolves to 198.54.114.239, announced in 198.54.114.0/24 by NAMECHEAP-NET - Namecheap, Inc. in US. sandrevolution.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 · sandrevolution.comRouting diversity1.5/10Peering density4.6/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/sandrevolution.com

Resolution chain

IPv6 resolution

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

Attribution

namecheap

ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Contact emails
e0519c3169154c089ba25cf6386ec780.protect@whoisguard.com, 78168d2188724e0e8b9002fdbbaf111d.protect@withheldforprivacy.com, 98304278d56e465fb41217375e1807be.protect@withheldforprivacy.com

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

  • dns1.namecheaphosting.com
  • dns2.namecheaphosting.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

  • d275363a.ess.barracudanetworks.com
  • d275363b.ess.barracudanetworks.com

SPF policy

  • include: spf.ess.barracudanetworks.com
  • include: spf.protection.outlook.com
  • a: sandrevolution.com
  • mx: sandrevolution.com
  • include: spf.web-hosting.com
  • ip: 198.54.114.111
  • ip: 198.54.114.239
  • ip: 198.54.116.239

Threat-feed evidence

History

Related pages

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