Skip to content

Hostname

indogold.id

Last fetched

indogold.id resolves to 147.139.178.154, announced in 147.139.128.0/18 by ALIBABA-CN-NET - Alibaba (US) Technology Co., Ltd. in ID. indogold.id 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 · indogold.idRouting diversity1.5/10Peering density7.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.0/10canon.whisper.security/host/indogold.id

Resolution chain

IPv6 resolution

No AAAA record for indogold.id is recorded in WhisperGraph.

Attribution

hangzhou alibaba advertising

ORIGIN_AS

WHOIS identity

Registrar
iana:1

Subdomains

Subdomain
apiv2.indogold.id
apiv3.indogold.id
blog.indogold.id
em.indogold.id
link.indogold.id
mail.indogold.id
roadmap.indogold.id
stglink.indogold.id
support.indogold.id
webmail.indogold.id
www.indogold.id

Showing 11 of 13. View all subdomains →

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns1.softlayer.com
  • ns2.softlayer.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

  • include: _spf.google.com
  • include: spf.mandrillapp.com
  • include: mail.zendesk.com

Threat-feed evidence

History

Related pages

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