Hostname
trioteca.com
Last fetched
trioteca.com resolves to 13.37.177.145, announced in 13.36.0.0/14 by AMAZON-02 - Amazon.com, Inc. in FR. trioteca.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 13.37.177.145
13.36.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Paris, FR
- 13.37.203.157
13.36.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Paris, FR
- 13.37.31.66
13.36.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Paris, FR
- 13.39.178.248
13.36.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Paris, FR
- 15.236.52.98
15.236.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Paris, FR
- 35.181.131.228
35.181.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Paris, FR
- 35.181.196.247
35.181.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Paris, FR
- 35.181.222.122
35.181.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Paris, FR
IPv6 resolution
No AAAA record for trioteca.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:146
- Registrant organisation
- domains by proxy,
- Contact emails
- trioteca.com@domainsbyproxy.com
Subdomains
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
- ns-267.awsdns-33.com
- ns-961.awsdns-56.net
- ns-1194.awsdns-21.org
- ns-1869.awsdns-41.co.uk
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
SPF policy
- include: _spf.google.com
- include: _spf.atlassian.net
Threat-feed evidence
History
Related pages
Pivot from trioteca.com 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: "trioteca.com"})-[: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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.