Skip to content

Hostname

remonon.com

Last fetched

remonon.com resolves to 108.138.85.29, announced in 108.138.80.0/21 by AMAZON-02 - Amazon.com, Inc. in US. remonon.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 · remonon.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.9/10canon.whisper.security/host/remonon.com

Resolution chain

IPv6 resolution

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of remonon.com owner
Contact emails
05dfae45-a55d-48c7-a4c4-a888908c0f7e@identity-protect.org, 10a7fc97-218d-4bbc-b951-07af718ae60b@identity-protect.org, 2ba80c5c-f4f8-424f-888b-def5b3b99bc4@identity-protect.org, 8068abcc-1819-4414-bad8-45fd90e9e9f0@identity-protect.org, 88f63661-5323-4cf9-b4e8-d8395ce51659@identity-protect.org, f4648e32-40bd-4c5a-8ebc-04cfa5ab3e63@identity-protect.org, owner-4659594@remonon.com.whoisprivacyservice.org

Subdomains

Mail and authentication

Nameservers

  • ns-15.awsdns-01.com
  • ns-213.awsdns-26.com
  • ns-545.awsdns-04.net
  • ns-880.awsdns-46.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-1240.awsdns-27.org
  • ns-1490.awsdns-58.org
  • ns-1778.awsdns-30.co.uk
  • ns-2005.awsdns-58.co.uk

MX records

  • remonon-com.mail.protection.outlook.com

SPF policy

  • include: amazonses.com
  • include: spf.protection.outlook.com
  • include: zohomail.eu
  • include: eu.transmail.net

Threat-feed evidence

History

Related pages

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