Skip to content

Hostname

optimize.pt

Last fetched

optimize.pt resolves to 108.128.146.200, announced in 108.128.0.0/13 by AMAZON-02 - Amazon.com, Inc. in IE. optimize.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 · optimize.ptRouting diversity2.4/10Peering density9.6/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.3/10canon.whisper.security/host/optimize.pt

Resolution chain

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrant organisation
optimize investment partners-sociedade gestora de fundos de investimento mobili?rio,s.a.
Contact emails
dep_informatico@optimize.pt

Subdomains

Subdomain
app.optimize.pt
clientes.optimize.pt
empresas.optimize.pt
ex.optimize.pt
optiprin.optimize.pt
private.optimize.pt
repositorio.optimize.pt
suporte.optimize.pt
www.optimize.pt

Showing 9 of 10. 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-58.awsdns-07.com
  • ns-577.awsdns-08.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
  • ns-1142.awsdns-14.org
  • ns-1730.awsdns-24.co.uk

MX records

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

SPF policy

  • include: spf.mailjet.com
  • include: spf.protection.outlook.com
  • mx: optimize.pt
  • ip: 212.83.171.184
  • ip: 212.83.171.185
  • ip: 212.83.171.200
  • ip: 85.139.252.226
  • ip: 93.108.235.6

Threat-feed evidence

History

Related pages

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