Skip to content

Hostname

palcomtech.ac.id

Last fetched

palcomtech.ac.id resolves to 34.120.190.48, announced in 34.120.0.0/14 by GOOGLE-CLOUD-PLATFORM - Google LLC in US. palcomtech.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 · palcomtech.ac.idRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/palcomtech.ac.id

Resolution chain

IPv6 resolution

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

Attribution

Google

cloud · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for palcomtech.ac.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
1.palcomtech.ac.id
406.palcomtech.ac.id
adakuis.palcomtech.ac.id
adminqtva.palcomtech.ac.id
ads1.palcomtech.ac.id
ak.palcomtech.ac.id
aula.palcomtech.ac.id
ayokitakuliah.palcomtech.ac.id
baak.palcomtech.ac.id
bakuliah.palcomtech.ac.id
beasiswa.palcomtech.ac.id
berita.palcomtech.ac.id

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

  • ns1.siteground.net
  • ns2.siteground.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: palcomtech.ac.id
  • mx: palcomtech.ac.id
  • include: palcomtech.ac.id.spf.auto.dnssmarthost.net
  • ip: 35.213.137.215

Threat-feed evidence

History

Related pages

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