Skip to content

Hostname

remax.com.ec

Last fetched

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

Resolution chain

IPv6 resolution

No AAAA record for remax.com.ec is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
registrar:ascio technologies inc.registration url: www.ascio.com|address: islands brygge 55|dk-2300, copenhagen s|country: dk|
Registrant organisation
remax international
Contact emails
domains@remax.net

Subdomains

Subdomain
220-server.remax.com.ec
info.remax.com.ec
mail.remax.com.ec
new.remax.com.ec
offices.remax.com.ec
server.remax.com.ec
webmail.remax.com.ec
www.remax.com.ec

Showing 8 of 8 subdomains (8 per page).

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-78.awsdns-09.com
  • ns-985.awsdns-59.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-1479.awsdns-56.org
  • ns-1989.awsdns-56.co.uk

MX records

  • mail.remax.com.ec

SPF policy

  • a: remax.com.ec
  • mx: remax.com.ec
  • ip: 38.129.136.26
  • ip: 38.129.136.8

Threat-feed evidence

History

Related pages

Pivot from remax.com.ec 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: "remax.com.ec"})-[: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.