Skip to content

Hostname

ufm.edu

Last fetched

ufm.edu resolves to 13.223.170.80, announced in 13.216.0.0/13 by AMAZON-AES - Amazon.com, Inc. in US. ufm.edu 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 · ufm.eduRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint4.6/10canon.whisper.security/host/ufm.edu

Resolution chain

IPv6 resolution

No AAAA record for ufm.edu is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrant organisation
universidad francisco marroquin

Subdomains

Subdomain
actonmadrid.ufm.edu
actonmba.ufm.edu
actonvrs.ufm.edu
admisiones.ufm.edu
ahgua.ufm.edu
akademeia.ufm.edu
alumni.ufm.edu
antiguaforum.ufm.edu
apidental.ufm.edu
arboretum.ufm.edu
arquitectura.ufm.edu
asig1.ufm.edu

Showing 12 of 187. View all subdomains →

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-372.awsdns-46.com
  • ns-575.awsdns-07.net
  • ns-1168.awsdns-18.org
  • ns-2042.awsdns-63.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • smtp.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com
  • aspmx4.googlemail.com
  • aspmx5.googlemail.com

SPF policy

  • include: amazonses.com
  • include: _spf.google.com
  • include: aspmx.pardot.com
  • include: _spf.salesforce.com
  • a: revista-medicina.ufm.edu
  • include: servers.mcsv.net
  • ip: 34.199.170.119
  • ip: 34.227.4.85
  • ip: 54.163.244.169

Threat-feed evidence

History

Related pages

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