Skip to content

Hostname

prindo.es

Last fetched

prindo.es resolves to 103.51.228.151, announced in 103.51.228.0/22 by LEWTELNET - LEW TelNet GmbH in DE. prindo.es 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 · prindo.esRouting diversity2.4/10Peering density5.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.0/10canon.whisper.security/host/prindo.es

Resolution chain

IPv6 resolution

No AAAA record for prindo.es is recorded in WhisperGraph.

Attribution

lew telnet

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for prindo.es. 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
cdn.prindo.es
new.prindo.es
news.prindo.es
psst.prindo.es
sst.prindo.es
www.prindo.es

Showing 6 of 8. View all subdomains →

Mail and authentication

Nameservers

  • ns1.media-concept.com
  • ns2.media-concept.com
  • 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

  • mailgw.media-concept.com
  • mailgw2.media-concept.com

SPF policy

  • ip: 62.159.108.0/24
  • ip: 195.24.116.0/24
  • ip: 103.51.228.0/24
  • ip: 62.157.164.144/28
  • ip: 2001:608:800:3c1::/64
  • ip: 2003:62:e049::/48
  • ip: 212.118.204.224/28
  • ip: 2a02:f90:23::/48
  • include: _spf.jupiter.salesmanago.pl

Threat-feed evidence

History

Related pages

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