Skip to content

Hostname

poderjudicial.pr

Last fetched

poderjudicial.pr resolves to 20.231.102.225, announced in 22.5.0.0/16 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in US. poderjudicial.pr 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 · poderjudicial.prRouting diversity1.5/10Peering density8.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/poderjudicial.pr

Resolution chain

IPv6 resolution

No AAAA record for poderjudicial.pr is recorded in WhisperGraph.

Attribution

Azure

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:801386
Registrant organisation
jose lezcano
Contact emails
nicadmin@ramajudicial.pr

Subdomains

Subdomain
cms.poderjudicial.pr
dts.poderjudicial.pr
ems.poderjudicial.pr
estudiosvirtuales.poderjudicial.pr
lms.poderjudicial.pr
test.poderjudicial.pr
www.poderjudicial.pr

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

  • ns-329.awsdns-41.com
  • ns-683.awsdns-21.net
  • ns-1321.awsdns-37.org
  • ns-1778.awsdns-30.co.uk

MX records

  • poderjudicial-pr.mail.protection.outlook.com

SPF policy

  • ip: 40.114.3.121/32
  • ip: 64.178.216.71/32
  • ip: 64.178.216.72/32
  • include: emcroute.com
  • include: spf.protection.outlook.com
  • include: mx.evertecinc.net
  • include: mxlogic.net
  • a: mail2.ramajudicial.pr
  • mx: mail3.ramajudicial.pr
  • ip: 13.92.29.15
  • ip: 196.12.181.26
  • ip: 64.178.216.78
  • ip: 64.178.216.86
  • ip: 64.178.216.93
  • ip: 64.178.216.94

Threat-feed evidence

History

Related pages

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