Hostname
redirect.talkbird.com
Last fetched
redirect.talkbird.com resolves to 3.164.85.103, announced in 3.164.84.0/23 by AMAZON-02 - Amazon.com, Inc. in FR. redirect.talkbird.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
- 3.164.85.103
3.164.84.0/23 · AMAZON-02 - Amazon.com, Inc. · Marseille, FR
- 3.164.85.11
3.164.84.0/23 · AMAZON-02 - Amazon.com, Inc. · Marseille, FR
- 3.164.85.37
3.164.84.0/23 · AMAZON-02 - Amazon.com, Inc. · Marseille, FR
- 3.164.85.47
3.164.84.0/23 · AMAZON-02 - Amazon.com, Inc. · Marseille, FR
- 52.85.65.33
52.85.64.0/22 · AMAZON-02 - Amazon.com, Inc. · Munich, DE
- 52.85.65.39
52.85.64.0/22 · AMAZON-02 - Amazon.com, Inc. · Munich, DE
- 52.85.65.54
52.85.64.0/22 · AMAZON-02 - Amazon.com, Inc. · Munich, DE
- 52.85.65.78
52.85.64.0/22 · AMAZON-02 - Amazon.com, Inc. · Munich, DE
IPv6 resolution
No AAAA record for redirect.talkbird.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for redirect.talkbird.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.
Mail and authentication
Nameservers
- 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
Threat-feed evidence
History
Related pages
Pivot from redirect.talkbird.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: "redirect.talkbird.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.