Skip to content

Hostname

matrizauto.pt

Last fetched

matrizauto.pt resolves to 94.23.75.179, announced in 94.23.0.0/16 by OVH - OVH SAS in PT. matrizauto.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 · matrizauto.ptRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.2/10canon.whisper.security/host/matrizauto.pt

Resolution chain

IPv6 resolution

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

Attribution

ovh

ORIGIN_AS

WHOIS identity

Registrant organisation
matrizauto comércio de automóveis lda
Contact emails
cgoncalves@japautomotive.pt

Subdomains

Subdomain
campanha.matrizauto.pt
campanhas.matrizauto.pt
guidelines.matrizauto.pt
newsletter.matrizauto.pt
vendaoseucarro.matrizauto.pt
www.matrizauto.pt

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

  • 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
  • ns1.ptempresas.pt
  • ns10.ptempresas.pt
  • ns2.ptempresas.pt

MX records

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

SPF policy

  • include: _spf.out.byside.com
  • include: _spf.kmitd.com
  • include: spf.protection.outlook.com
  • include: eu.transmail.net
  • include: eu.zcsend.net
  • mx: matrizauto.pt
  • ip: 5.39.74.24
  • ip: 62.28.158.70

Threat-feed evidence

History

Related pages

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