Skip to content

Hostname

limedika.lt

Last fetched

limedika.lt resolves to 80.209.232.186, announced in 80.209.224.0/20 by Interneto-vizija - UAB "Interneto vizija" in LT. limedika.lt 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 · limedika.ltRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.0/10canon.whisper.security/host/limedika.lt

Resolution chain

IPv6 resolution

No AAAA record for limedika.lt is recorded in WhisperGraph.

Attribution

uab interneto vizija

ORIGIN_AS

WHOIS identity

Registrar
registrar:uab 'interneto vizija'
Registrant organisation
uab 'interneto vizija'

Subdomains

Subdomain
avent.limedika.lt
didmena.limedika.lt
fortimail.limedika.lt
kasperskyeg.limedika.lt
mail.limedika.lt
o365.limedika.lt
pastas.limedika.lt
share.limedika.lt
tiekejai.limedika.lt
www.limedika.lt

Showing 10 of 11. 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

  • ns1.dns-parking.com
  • ns2.dns-parking.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

  • fortimail.limedika.lt
  • o365.limedika.lt
  • pastas.limedika.lt

SPF policy

  • include: spf.protection.outlook.com
  • include: survey.synopticom.com
  • a: limedika.lt
  • mx: limedika.lt
  • ip: 82.135.254.7

Threat-feed evidence

History

Related pages

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