Skip to content

Hostname

diskusiskripsi.com

Last fetched

diskusiskripsi.com resolves to 103.25.222.11, announced in 103.25.222.0/23 by EXBCOID-AS-AP - PT. EXABYTES NETWORK INDONESIA in ID. diskusiskripsi.com 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 · diskusiskripsi.comRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.8/10canon.whisper.security/host/diskusiskripsi.com

Resolution chain

IPv6 resolution

No AAAA record for diskusiskripsi.com is recorded in WhisperGraph.

Attribution

pt exabytes indonesia

ORIGIN_AS

WHOIS identity

Registrar
iana:303
Registrant organisation
didot supeno
Contact emails
teaminfoskripsi@gmail.com, contact@privacyprotect.org

Subdomains

Subdomain
cpanel.diskusiskripsi.com
mail.diskusiskripsi.com
webdisk.diskusiskripsi.com
webmail.diskusiskripsi.com
www.diskusiskripsi.com

Showing 5 of 5 subdomains (5 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

Sample outbound links

Mail and authentication

Nameservers

  • dns1.masterweb.com
  • dns3.masterweb.com
  • dns1.masterwebnet.com
  • dns3.masterwebnet.com
  • dns4.masterwebnet.com
  • dns2.masterweb.net
  • dns4.masterweb.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

  • mail.diskusiskripsi.com

SPF policy

  • a: diskusiskripsi.com
  • mx: diskusiskripsi.com

Threat-feed evidence

History

Related pages

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