Skip to content

Hostname

puig.es

Last fetched

puig.es resolves to 216.22.10.137, announced in 216.22.0.0/18 by LEASEWEB-USA-WDC - Leaseweb USA, Inc. in US. puig.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 · puig.esRouting diversity1.5/10Peering density3.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.3/10canon.whisper.security/host/puig.es

Resolution chain

IPv6 resolution

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

Attribution

leaseweb usa

ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for puig.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
autodiscover.puig.es
correo.puig.es
exc.puig.es
integra.puig.es
mail-ib-1.puig.es
mail-ib-ip-1.puig.es
mail-mx-1.puig.es
mail-mx-2.puig.es
mail-mx-3.puig.es
mta.puig.es
vcse.puig.es
webmail.puig.es

Showing 12 of 13. View all subdomains →

Mail and authentication

Nameservers

  • a.ns14.net
  • b.ns14.net
  • c.ns14.net
  • d.ns14.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

  • mx1.hc1069-92.c3s2.iphmx.com
  • mx2.hc1069-92.c3s2.iphmx.com
  • mail-mx-1.puig.es
  • mail-mx-2.puig.es

SPF policy

  • include: _u.puig.es._spf.smart.ondmarc.com
  • mx: puig.es

Threat-feed evidence

History

Related pages

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