Skip to content

Hostname

amorelation.com

Last fetched

amorelation.com resolves to 104.18.20.58, announced in 104.18.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. amorelation.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 · amorelation.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/amorelation.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1387
Registrant organisation
c/o whoisproxy.com
Contact emails
7676d6078a@amorelation.com.whoistrustee.com, 2b76e855d42489e7e1161888e7cd5e2fe664083f4974ae3477d0dbfe8588225c@amorelation.com.whoisproxy.org, 4809a324f71f6295f556748e773543d5c1ab8ac0872c3347785c988aab661e65@amorelation.com.whoisproxy.org, 93c4a5a81c8e27b7c1b67695da322b84e2bc5dc0ad9a84298b8c8c267448c042@amorelation.com.whoisproxy.org, da848a8a16b0af2d9b23454e1b3ed116e0e296d9163a0318e2d534072feb170a@amorelation.com.whoisproxy.org

Subdomains

Subdomain
n.amorelation.com

Showing 1 of 1 subdomain (1 per page).

Mail and authentication

Nameservers

  • josh.ns.cloudflare.com
  • rayne.ns.cloudflare.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

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • include: _spf.google.com
  • include: mail.zendesk.com
  • include: spf.sendios.io

Threat-feed evidence

History

Related pages

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