Skip to content

Hostname

dengage.net

Last fetched

dengage.net resolves to 18.220.21.15, announced in 18.220.0.0/14 by AMAZON-02 - Amazon.com, Inc. in US. dengage.net 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 · dengage.netRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.3/10canon.whisper.security/host/dengage.net

Resolution chain

IPv6 resolution

No AAAA record for dengage.net is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
domains by proxy,

Subdomains

Subdomain
banking.dengage.net
cdmp-eu-mx.dengage.net
cdmp-tr-mx.dengage.net
cdmp-us-mx.dengage.net
engines.dengage.net

Showing 5 of 1,063. View all subdomains →

Mail and authentication

Nameservers

  • ns-cloud-d1.googledomains.com
  • ns-cloud-d2.googledomains.com
  • ns-cloud-d3.googledomains.com
  • ns-cloud-d4.googledomains.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

  • 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

  • ip: 209.85.220.0/24
  • include: _spf.google.com
  • include: spf.zoho.com
  • include: _spf.engines.dengage.net
  • include: transmail.net
  • ip: 185.14.23.91
  • ip: 3.17.231.199
  • ip: 46.31.144.70
  • ip: 52.57.81.1

Threat-feed evidence

History

Related pages

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