Skip to content

Hostname

rootevidence.com

Last fetched

rootevidence.com resolves to 13.227.192.108, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. rootevidence.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 · rootevidence.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint6.3/10canon.whisper.security/host/rootevidence.com

Resolution chain

IPv6 resolution

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of rootevidence.com owner
Contact emails
waltergronli@gmail.com, 313ea805-3ee9-4536-8d4b-2e2c574e8adc@identity-protect.org

Subdomains

Subdomain
blackhat.rootevidence.com
capig.rootevidence.com
core.rootevidence.com
eng.rootevidence.com
interactsh.rootevidence.com
new.rootevidence.com
notifications.rootevidence.com
sandbox.rootevidence.com
scanner-info.rootevidence.com
sgtm.rootevidence.com
staging-core.rootevidence.com
team.rootevidence.com

Showing 12 of 18. View all subdomains →

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

  • ns-434.awsdns-54.com
  • ns-443.awsdns-55.com
  • ns-596.awsdns-10.net
  • ns-755.awsdns-30.net
  • ns-1196.awsdns-21.org
  • ns-1502.awsdns-59.org
  • ns-1841.awsdns-38.co.uk
  • ns-1979.awsdns-55.co.uk

MX records

  • smtp.google.com

SPF policy

  • include: _spf.google.com

Threat-feed evidence

History

Related pages

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