Hostname
adieu.com
Last fetched
adieu.com resolves to 3.162.163.110, announced in 3.162.160.0/22 by AMAZON-02 - Amazon.com, Inc. in US. adieu.com is listed by 1 threat feed; reconciled level HIGH.
Threat posture
40threat score (procedure-native scale)
HIGHListed by 1 threat feed. At least one source recommends blocking.
- Threat feeds listing this
- 1
- Verdict coverage
- malicious-evidenced
- First seen on a feed
- Wed, 26 Aug 2026 14:55:42 GMT
- Last seen on a feed
- Sun, 13 Sep 2026 23:27:23 GMT
Nutrition Label
Resolution chain
- 3.162.163.110
3.162.160.0/22 · AMAZON-02 - Amazon.com, Inc. · Chicago, US
- 3.162.163.28
3.162.160.0/22 · AMAZON-02 - Amazon.com, Inc. · Chicago, US
- 3.162.163.37
3.162.160.0/22 · AMAZON-02 - Amazon.com, Inc. · Chicago, US
- 3.162.163.65
3.162.160.0/22 · AMAZON-02 - Amazon.com, Inc. · Chicago, US
- 3.164.163.12
3.164.160.0/22 · AMAZON-02 - Amazon.com, Inc. · Paris, FR
- 3.164.163.46
3.164.160.0/22 · AMAZON-02 - Amazon.com, Inc. · Paris, FR
- 3.164.163.48
3.164.160.0/22 · AMAZON-02 - Amazon.com, Inc. · Paris, FR
- 3.164.163.54
3.164.160.0/22 · AMAZON-02 - Amazon.com, Inc. · Paris, FR
- 99.84.152.31
99.84.152.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 99.84.152.45
99.84.152.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 99.84.152.62
99.84.152.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 99.84.152.99
99.84.152.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
IPv6 resolution
No AAAA record for adieu.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:146
- Registrant organisation
- development services
- Contact emails
- admin@telepathy.com
Mail and authentication
Nameservers
- ns-275.awsdns-34.com
- ns-930.awsdns-52.net
- ns-1330.awsdns-38.org
- ns-1982.awsdns-55.co.uk
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- aspmx2.googlemail.com
- aspmx3.googlemail.com
Threat-feed evidence
History
Related pages
Pivot from adieu.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: "adieu.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.