Skip to content

Hostname

loma.ml

Last fetched

loma.ml resolves to 89.58.36.108, announced in 89.58.36.0/22 by netcup-AS - netcup GmbH in DE. loma.ml 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 · loma.mlRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint7.4/10canon.whisper.security/host/loma.ml

Resolution chain

IPv6 resolution

Attribution

netcup

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for loma.ml. 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
jabber.loma.ml
mail.loma.ml
matomo.loma.ml
mta-sts.loma.ml
munin.loma.ml
node.loma.ml
promo.loma.ml
www.loma.ml

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

Mail and authentication

Nameservers

  • ns1.1984hosting.com
  • ns2.1984hosting.com
  • ns0.1984.is
  • ns1.1984.is
  • ns2.1984.is
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • f.root-servers.net
  • h.root-servers.net
  • k.root-servers.net
  • m.root-servers.net

MX records

  • mail.loma.ml

SPF policy

  • a: loma.ml
  • mx: loma.ml
  • ip: 2a03:4000:65:f0d:589d:f2ff:fe1b:8458
  • ip: 89.58.36.108

Threat-feed evidence

History

Related pages

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