Skip to content

Hostname

mayatama.net

Last fetched

mayatama.net resolves to 103.16.132.162, announced in 103.16.132.0/24 by IDNIC-MAYATAMA-AS-ID - PT Mayatama Solusindo in ID. mayatama.net 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 · mayatama.netRouting diversity2.4/10Peering density3.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint5.2/10canon.whisper.security/host/mayatama.net

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1675
Registrant organisation
contact privacy inc. customer 0146888574
Contact emails
m4y4t4m4@gmail.com, mayatama.net@contactprivacy.com

Subdomains

Subdomain
1.mayatama.net
10.mayatama.net
2.mayatama.net
20.mayatama.net
3.mayatama.net
4.mayatama.net
5.mayatama.net
6.mayatama.net
7.mayatama.net
8.mayatama.net
9.mayatama.net
ads.mayatama.net

Showing 12 of 46. 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

Mail and authentication

Nameservers

  • lex.ns.cloudflare.com
  • pam.ns.cloudflare.com
  • ns1.mayatama.net
  • ns2.mayatama.net
  • ns3.mayatama.net

MX records

  • cleaner.mayatama.net
  • cleaner2.mayatama.net
  • cleaner3.mayatama.net

SPF policy

  • ip: 103.16.132.0/24
  • ip: 203.153.20.0/24
  • ip: 103.102.249.0/24
  • include: _spf.google.com
  • a: mayatama.net
  • mx: mayatama.net
  • mx: dns1.mayatama.net
  • ip: 103.16.132.17

Threat-feed evidence

History

Related pages

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