Skip to content

Hostname

d-map.co

Last fetched

d-map.co resolves to 37.19.112.12, announced in 37.19.112.0/24 by TRIPLEC-ASN - Triple C Cloud Computing Ltd. in IL. d-map.co 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 · d-map.coRouting diversity1.5/10Peering density3.6/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.0/10canon.whisper.security/host/d-map.co

Resolution chain

IPv6 resolution

No AAAA record for d-map.co is recorded in WhisperGraph.

Attribution

triple computing

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for d-map.co. 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
abie.d-map.co
all-pr.d-map.co
aluminum.d-map.co
avital-horef.d-map.co
axi-ravakiva.d-map.co
din.d-map.co
dnegrarim.d-map.co
dor3optic.d-map.co
drgalavishai.d-map.co
el-rubian-meat.d-map.co
ewar.d-map.co
galeykor.d-map.co

Showing 12 of 25. View all subdomains →

Mail and authentication

Nameservers

  • aleena.ns.cloudflare.com
  • lars.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

MX records

  • dmap-co0c.mail.protection.outlook.com
  • relay.d.co.il
  • relay2.d.co.il

SPF policy

  • include: spf.protection.outlook.com

Threat-feed evidence

History

Related pages

Pivot from d-map.co 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: "d-map.co"})-[: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.