Skip to content

Hostname

123ink.gr

Last fetched

123ink.gr resolves to 193.164.144.72, announced in 193.164.144.0/24 by DUOCAST-AS - Duocast B.V. in NL. 123ink.gr 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 · 123ink.grRouting diversity1.5/10Peering density6.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.0/10canon.whisper.security/host/123ink.gr

Resolution chain

IPv6 resolution

No AAAA record for 123ink.gr is recorded in WhisperGraph.

Attribution

duocast

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for 123ink.gr. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

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

  • 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.digitalrevolution.nl
  • ns2.digitalrevolution.nl

MX records

  • 123ink-gr.mail.protection.outlook.com
  • mx1.digitalrevolution.nl
  • mx2.digitalrevolution.nl
  • mx3.digitalrevolution.nl
  • mx4.digitalrevolution.nl

SPF policy

  • include: spf.protection.outlook.com
  • ip: 193.164.144.10
  • ip: 193.164.144.11
  • ip: 193.164.144.12
  • ip: 193.164.144.9
  • ip: 89.188.0.19

Threat-feed evidence

History

Related pages

Pivot from 123ink.gr 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: "123ink.gr"})-[: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.