Hostname
tenderu.me
Last fetched
tenderu.me resolves to 18.66.122.68, announced in 18.66.120.0/21 by AMAZON-02 - Amazon.com, Inc. in DE. tenderu.me 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
- 18.66.122.68
18.66.120.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.66.122.70
18.66.120.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.66.122.73
18.66.120.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.66.122.86
18.66.120.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.171.139.15
3.171.136.0/22 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 3.171.139.21
3.171.136.0/22 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 3.171.139.29
3.171.136.0/22 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 3.171.139.67
3.171.136.0/22 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 99.84.9.108
99.84.8.0/21 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 99.84.9.28
99.84.8.0/21 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 99.84.9.59
99.84.8.0/21 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 99.84.9.85
99.84.8.0/21 · AMAZON-02 - Amazon.com, Inc. · Dublin, IE
- 3.173.161.29
3.173.160.0/21 · AMAZON-02 - Amazon.com, Inc. · Amsterdam, NL
- 3.173.161.87
3.173.160.0/21 · AMAZON-02 - Amazon.com, Inc. · Amsterdam, NL
- 3.173.161.94
3.173.160.0/21 · AMAZON-02 - Amazon.com, Inc. · Amsterdam, NL
- 3.173.161.68
3.173.160.0/21 · AMAZON-02 - Amazon.com, Inc. · Amsterdam, NL
IPv6 resolution
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:1910
Subdomains
Mail and authentication
Nameservers
- rayden.ns.cloudflare.com
- teresa.ns.cloudflare.com
MX records
- mxbiz1.qq.com
- mxbiz2.qq.com
SPF policy
- include: spf.mail.qq.com
Threat-feed evidence
History
Related pages
Pivot from tenderu.me 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: "tenderu.me"})-[: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.