Skip to content

Hostname

namespedia.com

Last fetched

namespedia.com resolves to 217.195.155.44, announced in 217.195.152.0/22 by SHOCK-1 - Shock Hosting LLC in NL. namespedia.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 · namespedia.comRouting diversity1.5/10Peering density3.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/namespedia.com

Resolution chain

IPv6 resolution

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

Attribution

shock

ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
andrei sacinschi
Contact emails
ivatav@googlemail.com, c232741e5b8543fe9451b47d7c539396.protect@whoisguard.com, 0be603ed38f0440fbf720e594aa77d69.protect@withheldforprivacy.com, 4a2bfea7238f4058be748df5c0d1f973.protect@withheldforprivacy.com

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • dns1.registrar-servers.com
  • dns2.registrar-servers.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

  • eforward1.registrar-servers.com
  • eforward2.registrar-servers.com
  • eforward3.registrar-servers.com
  • eforward4.registrar-servers.com
  • eforward5.registrar-servers.com

SPF policy

  • include: spf.efwd.registrar-servers.com

Threat-feed evidence

History

Related pages

Pivot from namespedia.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: "namespedia.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.