Skip to content

Hostname

ifal.mx

Last fetched

ifal.mx resolves to 138.197.20.236, announced in 138.197.16.0/20 by DIGITALOCEAN-ASN - DigitalOcean, LLC in US. ifal.mx 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 · ifal.mxRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.2/10canon.whisper.security/host/ifal.mx

Resolution chain

IPv6 resolution

No AAAA record for ifal.mx is recorded in WhisperGraph.

Attribution

digitalocean

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for ifal.mx. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
backupsite.ifal.mx
bibliotecas.ifal.mx
cloud.ifal.mx
koha.ifal.mx
mail.ifal.mx
qa.ifal.mx
webmail.ifal.mx
www.ifal.mx

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

  • ns1.digitalocean.com
  • ns2.digitalocean.com
  • ns3.digitalocean.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

  • mx.zoho.com
  • mx2.zoho.com
  • mx3.zoho.com

SPF policy

  • ip: 200.76.57.81/28
  • include: spf.sendinblue.com
  • include: zohomail.com
  • mx: ifal.mx
  • a: mail.ifal.mx

Threat-feed evidence

History

Related pages

Pivot from ifal.mx 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: "ifal.mx"})-[: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.