Skip to content

Hostname

trivalor.pt

Last fetched

trivalor.pt resolves to 20.86.10.252, announced in 20.64.0.0/10 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in NL. trivalor.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 · trivalor.ptRouting diversity1.5/10Peering density8.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/trivalor.pt

Resolution chain

IPv6 resolution

No AAAA record for trivalor.pt is recorded in WhisperGraph.

Attribution

Github

saas · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for trivalor.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
autodiscover.trivalor.pt
azr-srv-10.trivalor.pt
cacifos.trivalor.pt
centosteste.trivalor.pt
comunicacao.trivalor.pt
consentimento.trivalor.pt
contactos.trivalor.pt
covidzero.trivalor.pt
emerge.trivalor.pt
faturacao.trivalor.pt
fit-faq.trivalor.pt
jobra-reservas.trivalor.pt

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

  • lx1-prm-dns-01.niodo.com
  • srv-ns-01.sogenave.pt

MX records

  • trivalor-pt.mail.protection.outlook.com

SPF policy

  • ip: 51.145.128.120/32
  • ip: 195.23.208.125/32
  • ip: 213.58.146.128/25
  • ip: 195.23.45.98/32
  • include: spf.emailsignatures365.com
  • include: spf.protection.outlook.com
  • include: successfactors.eu
  • include: servers.mcsv.net
  • mx: trivalor.pt

Threat-feed evidence

History

Related pages

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