Hostname
notifications.trustly.com
Last fetched
notifications.trustly.com resolves to 16.145.201.42, announced in 16.145.0.0/16 by AMAZON-02 - Amazon.com, Inc. in US. notifications.trustly.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
- 16.145.201.42
16.145.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Portland, US
- 16.148.142.219
16.148.128.0/17 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 35.84.234.73
35.80.0.0/12 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 35.86.56.95
35.80.0.0/12 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 44.240.128.50
44.224.0.0/11 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
- 52.34.38.139
52.32.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Boardman, US
IPv6 resolution
No AAAA record for notifications.trustly.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for notifications.trustly.com. 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 |
|---|
| int.notifications.trustly.com |
| sandbox.notifications.trustly.com |
| uat.notifications.trustly.com |
Showing 3 of 3 subdomains (3 per page).
Mail and authentication
Nameservers
- ns-154.awsdns-19.com
- ns-590.awsdns-09.net
- ns-1241.awsdns-27.org
- ns-1940.awsdns-50.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: amazonses.com
- include: spf.mandrillapp.com
Threat-feed evidence
History
Related pages
Pivot from notifications.trustly.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: "notifications.trustly.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.