Skip to content

Hostname

datix.ddme.dev

Last fetched

datix.ddme.dev resolves to 139.162.215.152, announced in 139.162.192.0/19 by AKAMAI-LINODE-AP - Akamai Connected Cloud in GB. datix.ddme.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 · datix.ddme.devRouting diversity1.5/10Peering density6.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint0.0/10canon.whisper.security/host/datix.ddme.dev

Resolution chain

IPv6 resolution

No AAAA record for datix.ddme.dev is recorded in WhisperGraph.

Attribution

akamai

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for datix.ddme.dev. 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

Subdomain
testing.datix.ddme.dev

Showing 1 of 2. View all subdomains →

Threat-feed evidence

History

Related pages

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