Skip to content

Hostname

amayamail.com

Last fetched

amayamail.com resolves to 72.183.217.213, announced in 72.176.0.0/13 by TWC-11427-TEXAS - Charter Communications Inc in US. amayamail.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 · amayamail.comRouting diversity1.5/10Peering density8.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint6.3/10canon.whisper.security/host/amayamail.com

Resolution chain

IPv6 resolution

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

Attribution

charter

ORIGIN_AS

WHOIS identity

Registrar
iana:1327
Registrant organisation
registration privacy, no-ip.com
Contact emails
0e0cf51a38b1716c-1099033@privacy.no-ip.com, 244ddada814e9390-1099033@privacy.no-ip.com, 25648e3aaf8c76a6-1099033@privacy.no-ip.com, 2613d86fce78774a-1099033@privacy.no-ip.com, 3447eabf85693d99-1099033@privacy.no-ip.com, 3a24d05997a5466b-1099033@privacy.no-ip.com, 4caa90bbb6edab7a-1099033@privacy.no-ip.com, 66f90bef704d1f35-1099033@privacy.no-ip.com, 94fba85cc55ef7ce-1099033@privacy.no-ip.com, 9851832ab79a3496-1099033@privacy.no-ip.com, a3c0b30c79c1af6e-1099033@privacy.no-ip.com, a85a0ddbdbfd53e1-1099033@privacy.no-ip.com, c5a260e636a41031-1099033@privacy.no-ip.com, cb8fc43bb103c451-1099033@privacy.no-ip.com, e2f8f3a82e20ce14-1099033@privacy.no-ip.com, e937bd4a6fd626f4-1099033@privacy.no-ip.com, tngtrsqpcv@whoisprivacyprotect.com, tyonuyy37639684@yeah.net

Mail and authentication

Nameservers

  • ns1.no-ip.com
  • ns2.no-ip.com
  • ns3.no-ip.com
  • ns4.no-ip.com
  • ns5.no-ip.com
  • static-1.no-ip.com
  • static-2.no-ip.com
  • static-3.no-ip.com

MX records

  • mail.protonmail.ch
  • mailsec.protonmail.ch

SPF policy

  • include: _spf.protonmail.ch
  • mx: amayamail.com

Threat-feed evidence

History

Related pages

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