Skip to content

Hostname

apik.net.id

Last fetched

apik.net.id resolves to 103.241.24.123, announced in 103.241.24.0/24 by IDNIC-PTAMI-AS-ID - APIK Media Networks in ID. apik.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 · apik.net.idRouting diversity1.5/10Peering density4.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint9.0/10canon.whisper.security/host/apik.net.id

Resolution chain

IPv6 resolution

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

Attribution

apik

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for apik.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
dns.apik.net.id
ns1.apik.net.id
ns2.apik.net.id
ns3.apik.net.id
ns4.apik.net.id
www.apik.net.id

Showing 6 of 6 subdomains (6 per page).

Mail and authentication

Nameservers

  • adi.ns.cloudflare.com
  • braden.ns.cloudflare.com
  • lily.ns.cloudflare.com
  • max.ns.cloudflare.com
  • dns1.apik.co.id
  • dns2.apik.co.id
  • dns3.apik.co.id
  • dns4.apik.co.id
  • pns101.cloudns.net
  • 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
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • a: apik.net.id
  • mx: apik.net.id
  • include: relay.mailbaby.net

Threat-feed evidence

History

Related pages

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