Skip to content

Hostname

meromed.dev

Last fetched

meromed.dev resolves to 158.160.30.139, announced in 158.160.0.0/16 by YandexCloud - Yandex.Cloud LLC in RU. meromed.dev 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 · meromed.devRouting diversity1.5/10Peering density5.5/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.3/10canon.whisper.security/host/meromed.dev

Resolution chain

IPv6 resolution

No AAAA record for meromed.dev is recorded in WhisperGraph.

Attribution

Yandex

esp · ORIGIN_AS

WHOIS identity

Registrar
iana:463
Registrant organisation
ooo ayti-tochka

Subdomains

Subdomain
dev.meromed.dev
error.meromed.dev
gitlab.meromed.dev
grafana.meromed.dev
icdn.meromed.dev
img.meromed.dev
medstudio.meromed.dev
meroplace.meromed.dev
pointreg.meromed.dev
proxy.meromed.dev
s.meromed.dev
signoz.meromed.dev

Showing 12 of 66. View all subdomains →

Mail and authentication

Nameservers

  • karina.ns.cloudflare.com
  • keenan.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
  • ns1.yandexcloud.net
  • ns2.yandexcloud.net

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • include: spf.unisender.ru

Threat-feed evidence

History

Related pages

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