Skip to content

Hostname

pla.net.py

Last fetched

pla.net.py resolves to 190.112.208.167, announced in 190.112.208.0/24 by AS263228 - PLANET S.A. in PY. pla.net.py 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 · pla.net.pyRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/pla.net.py

Resolution chain

IPv6 resolution

No AAAA record for pla.net.py is recorded in WhisperGraph.

Attribution

planet

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for pla.net.py. 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
aba.pla.net.py
alertas-xl.pla.net.py
apophis.pla.net.py
blue2.pla.net.py
cloud.pla.net.py
cpanel.pla.net.py
dns1-venus.pla.net.py
dns2-polaris.pla.net.py
eris.pla.net.py
gestioip.pla.net.py
iridium.pla.net.py
iris.pla.net.py

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

  • dns1-venus.pla.net.py
  • dns2-polaris.pla.net.py
  • ns1-venus.pla.net.py
  • ns2-polaris.pla.net.py

MX records

  • mail.pla.net.py

SPF policy

  • a: pla.net.py
  • mx: pla.net.py
  • ip: 190.112.208.2
  • ip: 201.217.19.2

Threat-feed evidence

History

Related pages

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