Skip to content

Hostname

lonas.ee

Last fetched

lonas.ee resolves to 80.208.230.125, announced in 80.208.224.0/21 by Interneto-vizija - UAB "Interneto vizija" in LT. lonas.ee 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 · lonas.eeRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.0/10canon.whisper.security/host/lonas.ee

Resolution chain

IPv6 resolution

No AAAA record for lonas.ee is recorded in WhisperGraph.

Attribution

uab interneto vizija

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for lonas.ee. 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
mail.lonas.ee
orders.lonas.ee
stage.lonas.ee
voida.lonas.ee
www.lonas.ee

Showing 5 of 5 subdomains (5 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

  • blair.ns.cloudflare.com
  • lamar.ns.cloudflare.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

  • lonas-ee.mail.protection.outlook.com

SPF policy

  • include: _spf.mlsend.com
  • include: spf.protection.outlook.com
  • mx: lonas.ee
  • include: mailgun.org
  • ip: 80.208.230.125
  • ip: 81.7.106.77

Threat-feed evidence

History

Related pages

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