Skip to content

Hostname

melsa.net.id

Last fetched

melsa.net.id resolves to 202.138.224.23, announced in 202.138.251.0/24 by MELSANET-ID-AP - Melsa-i-net AS in ID. melsa.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 · melsa.net.idRouting diversity1.5/10Peering density4.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/melsa.net.id

Resolution chain

IPv6 resolution

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

Attribution

melsanet id ap melsa net

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for melsa.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
absen.melsa.net.id
adha-wl.melsa.net.id
adm.melsa.net.id
aeon-lan.melsa.net.id
aero-ptdi.melsa.net.id
agatestudio.melsa.net.id
aje.melsa.net.id
alarm.melsa.net.id
alfonso-wl.melsa.net.id
amnesia-wl.melsa.net.id
andry.melsa.net.id
ap-cimahi3.melsa.net.id

Showing 12 of 750. 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.melsa.net.id
  • ns2.melsa.net.id
  • ns3.melsa.net.id
  • ns4.melsa.net.id

MX records

  • mail.melsa.net.id
  • mx2.melsa.net.id

SPF policy

  • ip: 202.138.224.0/24
  • ip: 202.138.225.0/24
  • ip: 202.138.226.0/24
  • include: aspmx.googlemail.com
  • a: melsa.co.id
  • a: melsa.id
  • a: melsa.net.id
  • mx: melsa.net.id
  • ip: 2403:9500:5:0:0:0:0:2

Threat-feed evidence

History

Related pages

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