Skip to content

Hostname

multidata.net.id

Last fetched

multidata.net.id resolves to 103.10.120.188, announced in 103.10.120.0/24 by SDI-AS-ID - PT Sumber Data Indonesia in ID. multidata.net.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 · multidata.net.idRouting diversity1.5/10Peering density4.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.0/10canon.whisper.security/host/multidata.net.id

Resolution chain

IPv6 resolution

No AAAA record for multidata.net.id is recorded in WhisperGraph.

Attribution

pt sumber indonesia

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for multidata.net.id. 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
billing.multidata.net.id
cacti.multidata.net.id
cpcontacts.multidata.net.id
dev-giga.multidata.net.id
giga.multidata.net.id
mail.multidata.net.id
mrtg.multidata.net.id
www.multidata.net.id

Showing 8 of 8 subdomains (8 per page).

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

Mail and authentication

Nameservers

  • ns3.sdi.net.id
  • ns4.sdi.net.id
  • a.misconfigured.dns.server.invalid

MX records

  • billing.multidata.net.id
  • pmg01.sdi.net.id

SPF policy

  • ip: 103.10.120.0/24
  • ip: 103.10.121.0/24
  • ip: 116.68.170.0/24
  • include: _spf.google.com
  • include: spf.saad.biz.id
  • ip: 103.10.120.187
  • ip: 114.198.245.228

Threat-feed evidence

History

Related pages

Pivot from multidata.net.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: "multidata.net.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.