Skip to content

Hostname

r2net.com

Last fetched

r2net.com resolves to 38.69.200.41, announced in 38.69.200.0/24 by AS393515 in US. r2net.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 · r2net.comRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/r2net.com

Resolution chain

IPv6 resolution

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

WHOIS identity

Registrar
iana:2
Registrant organisation
perfect privacy,
Contact emails
cm64j8un62m@networksolutionsprivateregistration.com, dj8nm7wu47b@networksolutionsprivateregistration.com, gm6eb7xj9r9@networksolutionsprivateregistration.com, kg2fk6ck3bw@networksolutionsprivateregistration.com, mx6ky6ba383@networksolutionsprivateregistration.com, qq4ty6498z9@networksolutionsprivateregistration.com, rv5855u7859@networksolutionsprivateregistration.com, t67kz6k54jm@networksolutionsprivateregistration.com, wk5y79v32qx@networksolutionsprivateregistration.com, yf3t88cv9u7@networksolutionsprivateregistration.com, yp3ty6bk2ru@networksolutionsprivateregistration.com, zb8dg4zc8st@networksolutionsprivateregistration.com

Subdomains

Mail and authentication

Nameservers

  • ns-371.awsdns-46.com
  • ns-702.awsdns-23.net
  • ns-1465.awsdns-55.org
  • ns-1617.awsdns-10.co.uk

MX records

  • us-smtp-inbound-1.mimecast.com
  • us-smtp-inbound-2.mimecast.com

SPF policy

  • ip: 148.105.0.0/16
  • ip: 198.2.128.0/18
  • ip: 205.201.128.0/20
  • ip: 212.29.208.34/32
  • include: spf.mandrillapp.com
  • include: us._netblocks.mimecast.com
  • include: spf.protection.outlook.com
  • a: r2net.com
  • mx: r2net.com
  • include: spf.mecloud.co.il
  • ip: 38.69.200.7

Threat-feed evidence

History

Related pages

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