Skip to content

Hostname

polnep.ac.id

Last fetched

polnep.ac.id resolves to 157.10.192.19, announced in 157.10.192.0/24 by IDNIC-POLNEP-AS-ID - Politeknik Negeri Pontianak in ID. polnep.ac.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 · polnep.ac.idRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.2/10canon.whisper.security/host/polnep.ac.id

Resolution chain

IPv6 resolution

No AAAA record for polnep.ac.id is recorded in WhisperGraph.

Attribution

politeknik negeri pontianak

ORIGIN_AS

WHOIS identity

Registrant organisation
boy gautama -
Contact emails
boy.gautama@gmail.com

Subdomains

Subdomain
aak.polnep.ac.id
ab.polnep.ac.id
ak.polnep.ac.id
arsitektur.polnep.ac.id
bawal.polnep.ac.id
btp.polnep.ac.id
cloud.polnep.ac.id
cumi.polnep.ac.id
edu.polnep.ac.id
ejurnal.polnep.ac.id
elektro.polnep.ac.id
epustaka.polnep.ac.id

Showing 12 of 57. 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.irza.net
  • ns2.irza.net
  • ns3.irza.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

  • smtp.google.com

SPF policy

  • include: _netblocks.google.com
  • include: _netblocks2.google.com
  • include: _spf.google.com
  • include: spf.protection.outlook.com
  • include: _spf.mailku.net

Threat-feed evidence

History

Related pages

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