Hostname
birdplaneapp.com
Last fetched
birdplaneapp.com resolves to 18.244.214.19, announced in 18.244.214.0/23 by AMAZON-02 - Amazon.com, Inc. in US. birdplaneapp.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
- 18.244.214.19
18.244.214.0/23 · AMAZON-02 - Amazon.com, Inc. · San Francisco, US
- 18.244.214.22
18.244.214.0/23 · AMAZON-02 - Amazon.com, Inc. · San Francisco, US
- 18.244.214.49
18.244.214.0/23 · AMAZON-02 - Amazon.com, Inc. · San Francisco, US
- 18.244.214.85
18.244.214.0/23 · AMAZON-02 - Amazon.com, Inc. · San Francisco, US
- 3.168.73.120
3.168.72.0/23 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 3.168.73.15
3.168.72.0/23 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 3.168.73.24
3.168.72.0/23 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 3.168.73.57
3.168.72.0/23 · AMAZON-02 - Amazon.com, Inc. · New York, US
IPv6 resolution
No AAAA record for birdplaneapp.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:470
- Registrant organisation
- bambuser ab
- Contact emails
- birdplaneapp.com-registrant@anonymised.email
Mail and authentication
Nameservers
- ns-110.awsdns-13.com
- ns-976.awsdns-58.net
- 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
- ns-1332.awsdns-38.org
- ns-1713.awsdns-22.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
Threat-feed evidence
History
Related pages
Pivot from birdplaneapp.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: "birdplaneapp.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.