Skip to content

Hostname

vente-unique.pt

Last fetched

vente-unique.pt resolves to 13.224.106.107, announced in 13.224.106.0/24 by AMAZON-02 - Amazon.com, Inc. in IT. vente-unique.pt 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 · vente-unique.ptRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/vente-unique.pt

Resolution chain

IPv6 resolution

No AAAA record for vente-unique.pt is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for vente-unique.pt. 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
emailtracking.vente-unique.pt
emartracking.vente-unique.pt
metrics.vente-unique.pt
nocache.vente-unique.pt
pp.vente-unique.pt
tdf1.vente-unique.pt
www.vente-unique.pt

Showing 7 of 9. 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

Sample outbound links

Mail and authentication

Nameservers

  • ns-294.awsdns-36.com
  • ns-590.awsdns-09.net
  • ns-1034.awsdns-01.org
  • ns-1873.awsdns-42.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • include: amazonses.com
  • include: _spf.google.com
  • include: spf.mailjet.com
  • a: vente-unique.pt
  • mx: vente-unique.pt
  • ip: 95.131.137.119
  • ip: 95.131.137.122

Threat-feed evidence

History

Related pages

Pivot from vente-unique.pt 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: "vente-unique.pt"})-[: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.