Hostname
digima.co.id
Last fetched
digima.co.id resolves to 103.16.199.29, announced in 103.16.199.0/24 by IDNIC-JALANET-AS-ID - PT. Jupiter Jala Arta in ID. digima.co.id is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
IPv6 resolution
No AAAA record for digima.co.id is recorded in WhisperGraph.
Attribution
pt jupiter jala arta
MAIL_RECEIVER, ORIGIN_AS
WHOIS identity
- Registrar
- iana:1
Subdomains
| Subdomain |
|---|
| mail.digima.co.id |
| www.digima.co.id |
Showing 2 of 2 subdomains (2 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
- ns1.hoster.co.id
- ns2.hoster.co.id
- ns3.hoster.co.id
- ns4.hoster.co.id
MX records
- digima.co.id
SPF policy
- a: digima.co.id
- mx: digima.co.id
- ip: 103.131.51.25
- ip: 103.131.51.29
- ip: 103.16.198.17
- ip: 103.16.198.170
- ip: 103.16.198.171
- ip: 103.16.198.174
- ip: 103.16.198.18
- ip: 103.16.198.55
- ip: 103.16.199.30
- ip: 103.251.44.212
- ip: 202.74.239.249
Threat-feed evidence
History
Related pages
Pivot from digima.co.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: "digima.co.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.