Skip to content

Hostname

elcode.moscow

Last fetched

elcode.moscow resolves to 80.251.142.60, announced in 80.251.128.0/20 by AS21446 - SOTEL LLC in RU. elcode.moscow 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 · elcode.moscowRouting diversity1.5/10Peering density3.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/elcode.moscow

Resolution chain

IPv6 resolution

No AAAA record for elcode.moscow is recorded in WhisperGraph.

Attribution

sotel

ORIGIN_AS

WHOIS identity

Registrar
iana:463
Registrant organisation
personal data, can not be publicly disclosed according to applicable laws.
Contact emails
noc@elcode.ru

Subdomains

Subdomain
ns.elcode.moscow
ns3.elcode.moscow

Showing 2 of 2 subdomains (2 per page).

Mail and authentication

Nameservers

  • ns.elcode.moscow
  • ns3.elcode.moscow
  • 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
  • agava.elcode.ru
  • ns.elcode.ru

MX records

  • ns.elcode.moscow

Threat-feed evidence

History

Related pages

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