Skip to content

Hostname

domainactive.org

Last fetched

domainactive.org resolves to 104.18.22.135, announced in 104.18.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. domainactive.org 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 · domainactive.orgRouting diversity3.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/domainactive.org

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:146
Registrant organisation
domain administrator
Contact emails
pw-07b7e5eb8caf0d4ffffaf010e35d23c2@privacyguardian.org, pw-4cee0663b16ba7e9376b8b8b95354330@privacyguardian.org

Subdomains

Subdomain
2.domainactive.org
9m.domainactive.org
admin.domainactive.org
apps.domainactive.org
bot.domainactive.org
careers.domainactive.org
cdn.domainactive.org
client.domainactive.org
clients.domainactive.org
cloud.domainactive.org
connect.domainactive.org
dev.domainactive.org

Showing 12 of 43. View all subdomains →

Mail and authentication

Nameservers

  • ns03.domaincontrol.com
  • ns04.domaincontrol.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
  • ns1.domainactive.org
  • ns2.domainactive.org

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

Threat-feed evidence

History

Related pages

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