Skip to content

Hostname

lugacom.com

Last fetched

lugacom.com resolves to 193.228.163.13, announced in 193.228.163.0/24 by RCK - STATE UNITARY ENTERPRISE OF THE LUGANSK PEOPLE'S REPUBLIC "LUGANSK COMMUNICATIONS" in RU. lugacom.com 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 · lugacom.comRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/lugacom.com

Resolution chain

IPv6 resolution

No AAAA record for lugacom.com is recorded in WhisperGraph.

Attribution

state unitary enterprise of lugansk people republic

ORIGIN_AS

WHOIS identity

Registrar
iana:1606
Registrant organisation
personal data, can not be publicly disclosed according to applicable laws.
Contact emails
admin@domainregistriesfoundation.com, dns.telematika@gmail.com, lugacom.com@regprivate.ru

Subdomains

Subdomain
admin.lugacom.com
dlr.lugacom.com
mail.lugacom.com
my.lugacom.com
ns1.lugacom.com
ns2.lugacom.com
pmt.lugacom.com
smpp.lugacom.com
www.lugacom.com

Showing 9 of 9 subdomains (9 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.lugacom.com
  • ns2.lugacom.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

  • mail.lugacom.com

SPF policy

  • a: lugacom.com
  • mx: lugacom.com

Threat-feed evidence

History

Related pages

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