Website profiles · Technology insights · Alternatives

adsb.im

ADSB Feeder Image - Airplane Tracking Made Simple

No paid content found
Visit website
Profile views 5 Outbound visits 0 Normal
ADSB.im Full homepage screenshot

At a glance

Category
Software & Apps
Language
English
Paid-content signal
No paid content foundObserved
Registered
Unknown
Hosting
HostHatch, LLCInferred
HTTPS certificate trusted
PassedObserved
Last updated

Website review

This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.

What is ADSB.im?

ADSB.im is the home of the ADS-B Feeder Image, a prebuilt software image that turns a single-board computer (like a Raspberry Pi) plus an SDR dongle and antenna into a receiver for aircraft, ships, weather balloons, and other radio signals. Rather than installing and configuring each decoder by hand, you flash one image to an SD card, boot the board, and manage everything through a web interface at http://adsb-feeder.local (or my.adsb.im if local name resolution doesn't work).

Its main appeal is breadth: the same image handles ADS-B (aircraft), AIS (ships), Sonde (weather balloons), and ACARS/VDL2/HFDL (aircraft-to-ground data), each with its own decoders and communities. It can plot what you receive on your own map and feed multiple aggregators at once — the project lists adsb.lol, ADS-B Exchange, FlightAware, FlightRadar24, OpenSky Network, Plane Finder, and many others.

Who it's for

  • Beginners who want a working feeder with minimal Linux knowledge; the SBC image is described as the most tested and least error-prone path.
  • Multi-interest hobbyists who want aircraft and ship tracking (or balloons) from one box instead of separate setups.
  • Feeders who want to contribute to several aggregators without maintaining several installs.

Installation paths, compared

Method Effort Best for
Single-board computer image Lowest Most users; the recommended default
DietPi Low Boards or setups where DietPi is already preferred
Generic Linux Higher Advanced users, existing servers, unusual hardware

The basic flow is the same: pick a supported board, attach an SDR dongle and antenna, write the matching image to an SD card, boot, and wait a few minutes (occasionally 15–20). If Wi-Fi wasn't configured during imaging, the feeder creates an adsb.im-feeder hotspot you can join to finish setup.

Next step: check the supported hardware list before buying anything, since the image is built for specific boards and dongles. If you already run a Raspberry Pi and have an SDR, start with the SBC image rather than the generic Linux route. For broader context on the hobby, see FlightAware or FlightRadar24, two of the aggregators this image can feed.

Which single board computers and SDR radio dongles are supported for setting up an ADSB.im feeder?

ADSB.im's own installation guidance is that the single-board-computer image is the best-tested and easiest path, and that you should start by choosing from its list of supported SBCs. The site names Raspberry Pi as the board most people use and says several other boards are supported, but it does not enumerate them in the material available here. Likewise, it tells you to add "an SDR radio dongle and an antenna" without listing specific dongle models.

What this means in practice

  • Board: treat Raspberry Pi as the safe default, since it is what most users run and therefore what gets the most real-world testing.
  • Dongle: any receive-only SDR covering the relevant band should work in principle, but the page does not confirm particular chipsets or models, so verify before buying.
  • If you already own a board that is not a Raspberry Pi, check the supported-hardware list before writing an image — a board that is not listed may still run the Linux install path, but with more manual setup.

Where to confirm the exact lists

The supported-hardware and FAQ pages are the authoritative source for both the board list and any dongle recommendations, since those change over time:

  • ADSB.im — main site with the hardware and FAQ sections
  • Raspberry Pi — official board documentation if you go the Pi route

A practical decision path

  1. Pick a board from the supported list, favouring a Raspberry Pi if you have no strong preference.
  2. Confirm the dongle is a receive-only SDR suited to the signal you want (ADS-B at 1090 MHz, or the relevant band for AIS, Sonde, ACARS/VDL2/HFDL).
  3. Download the matching SD-card image, write it, boot, and wait a few minutes — sometimes 15–20 minutes depending on board and image.
  4. Reach the feeder at http://adsb-feeder.local, or my.adsb.im if mDNS does not work on your network; if WiFi was not configured while writing the card, connect to the adsb.im-feeder hotspot first.

If your goal is simply to get aircraft on a map and share to aggregators, the SBC image plus a Raspberry Pi and a compatible dongle is the lowest-friction combination the project itself recommends.

How do I install and boot the ADSB Feeder Image on a Raspberry Pi or other SBC?

The ADSB Feeder Image is designed to be flashed to an SD card and booted on a supported single-board computer, after which you reach it through a browser rather than a monitor and keyboard.

Basic install path (SBC image)

  1. Pick a supported single-board computer. Raspberry Pi boards are the most commonly used and best tested; several other boards are supported.
  2. Connect an SDR radio dongle and an antenna.
  3. Download the SD-card image that matches your board.
  4. Write the image to an SD card.
  5. Boot the board and wait. This typically takes a few minutes, though some boards or images can take 15–20 minutes on first boot.
  6. Open http://adsb-feeder.local in a browser. If mDNS does not work on your network, use my.adsb.im, which should redirect you to your new feeder.

If you plan to use WiFi

If you could not configure WiFi while writing the SD card, the image creates a hotspot named adsb.im-feeder. Connect to that hotspot to finish setup.

Install options and trade-offs

Method Best for Trade-off
Single-board computer image Most users; first choice when unsure Requires a supported SBC and an SD card
DietPi Users already comfortable with DietPi Slightly less turnkey than the dedicated SBC image
Linux Advanced users running their own system Most manual setup and the most room for pitfalls

A practical next step

Before buying hardware, check the supported-hardware list on ADSB.im and confirm your board and SDR dongle are covered. If your board is listed and you have a spare SD card, the SBC image is the lowest-friction route; choose the Linux path only if you specifically want to run the feeder inside an existing system.

How do I connect to my ADSB.im feeder after boot and configure WiFi using the adsb.im-feeder hotspot?

After boot, connect to your feeder by browsing to http://adsb-feeder.local from a device on the same network. If your network doesn't resolve .local names (mDNS), go to my.adsb.im instead; it redirects you to your feeder's local address. For WiFi setup when you couldn't preconfigure it while writing the SD card, the image creates a hotspot named adsb.im-feeder — join that network first, then open the same addresses to reach the configuration page.

Typical first-run flow

  1. Write the matching SD-card image, insert it, and power on the single-board computer. Wait a few minutes; some boards and images take 15–20 minutes on first boot.
  2. On a phone or laptop, look for the WiFi network adsb.im-feeder and connect to it.
  3. Open http://adsb-feeder.local or my.adsb.im in a browser.
  4. Enter your home WiFi credentials in the web interface and save.
  5. The feeder reboots or switches networks; reconnect your device to your normal WiFi, then browse to the same address again to confirm it's online and feeding.

Wired Ethernet makes this simpler. If you have a cable run, plug it in before boot and skip the hotspot step entirely — the feeder should appear at adsb-feeder.local or via my.adsb.im right away. The hotspot path is mainly for headless setups where WiFi is the only option.

If nothing loads

  • Give it more time. First boot is slow on modest boards, especially while services initialize.
  • Confirm you're on the right network. adsb-feeder.local only works on the same LAN; the adsb.im-feeder hotspot is a separate network, so switch back after saving WiFi details.
  • Try the IP address directly if you can find it in your router's client list — useful when mDNS is blocked on your network.
  • Check that the SDR dongle and antenna are seated; the web interface should show whether the radio is detected, though basic connectivity works even before the radio is recognized.

This approach suits people who want a self-hosted receiver without editing config files by hand. The trade-off is that the hotspot step adds a couple of minutes and requires a second device (phone or laptop) to complete. For background on what the image supports beyond aircraft — ships via AIS, weather balloons via Sonde, and ACARS/VDL2/HFDL — see ADSB.im. If you're choosing hardware first, the supported single-board computer list there is the place to start.

Which flight tracking aggregators can I share my ADS-B data with using ADSB.im?

ADSB.im's feeder image is built to send your ADS-B data to many aggregators at once, so you are not locked into a single network. The page lists adsb.lol, Fly Italy Adsb, TheAirTraffic, adsb.fi, sdrmap, 1090MHz UK, ADS-B Exchange, ADSBHub, HPRadar, airplanes.live, AVDelphi, FlightAware, FlightRadar24, OpenSky Network, Plane.watch, Plane Finder, Planespotters.net, AirNav Radar, and Radar Virtuel, with "and more" indicating the list is not exhaustive. The same image also supports AIS for ships, Sonde for weather balloons, and ACARS/VDL2/HFDL, each with its own aggregators and communities.

How to choose aggregators

You usually do not have to pick just one. If your goal is maximum coverage, enable several; if you want to limit bandwidth or CPU on a small board, start with one or two.

Goal Reasonable starting point
Broad public coverage adsb.lol, adsb.fi, airplanes.live, TheAirTraffic
Commercial flight tracking FlightAware, FlightRadar24, Plane Finder
Research / open data OpenSky Network
Regional or niche communities Fly Italy Adsb, 1090MHz UK, Radar Virtuel, AVDelphi
Ship or balloon tracking AIS and Sonde aggregators, separate from ADS-B

A practical first step: install the image on a supported single-board computer, add an SDR dongle and antenna, then open the local web interface at http://adsb-feeder.local (or my.adsb.im) and enable the aggregators you care about from there.

Can ADSB.im track ships, weather balloons, or ACARS/VDL2/HFDL data in addition to aircraft?

Yes. ADSB.im is not limited to aircraft. Its page says the feeder image supports AIS for tracking ships, Sonde for weather balloons, and ACARS/VDL2/HFDL for receiving aircraft-to-ground data transmissions. It also notes that each of these areas has its own aggregators and communities, and that the common thread is easy setup through the Feeder Image.

H3 What this means in practice

  • Aircraft (ADS-B): Plot nearby planes on your own map and share with aggregators such as adsb.lol, TheAirTraffic, FlightAware and FlightRadar24.
  • Ships (AIS): Receive vessel transmissions and feed ship-tracking aggregators.
  • Weather balloons (Sonde): Track radiosonde balloons.
  • ACARS/VDL2/HFDL: Receive data transmissions from aircraft to ground stations.

H3 Choosing what to track If you mainly want aircraft, a standard ADS-B setup is enough. If you want ships or weather balloons, you will need the appropriate radio and antenna for those frequencies, and you will likely join different aggregator communities. ACARS/VDL2/HFDL is more of a data-decoding interest than simple map plotting.

H3 Next step Check the supported hardware page first to confirm your SBC and SDR dongle are compatible, then decide which signals you want to receive. The easiest path remains a single-board computer image, since the site says that is tested most and has the fewest pitfalls.

Related questions

More questions →
How do I access my ADSB.im feeder after first boot?

After the first boot, try http://adsb-feeder.local first. If that doesn't load, go to my.adsb.im, which redirects to your new feeder. If you planned to use WiFi but couldn't configure it while writing the SD card, the image creates a hotspot named adsb.im-feeder that you can connect to.

The three access paths, in order

1. Local address via mDNS (try first)

Open a browser on a device on the same network and go to:

http://adsb-feeder.local

This works when mDNS resolution is functioning on your home network. It's the fastest path because it talks directly to the feeder without any external service.

2. Redirect service (fallback)

If adsb-feeder.local doesn't resolve — common on networks that block or don't forward mDNS — use:

http://my.adsb.im

This should redirect you to your new ADS-B feeder. Use this when the local name fails but the feeder is otherwise reachable.

3. WiFi hotspot (when WiFi wasn't pre-configured)

If you intended to use WiFi and weren't able to set it up while writing the SD card, the image starts a hotspot:

  • SSID: adsb.im-feeder

Connect to that hotspot, then reach the feeder through the browser. This is the path for a headless setup where no wired Ethernet is available and no WiFi credentials were baked into the card.

Before you try any of these

The steps that come before access, per the project's install flow:

  1. Start with one of the supported single board computers.
  2. Add an SDR radio dongle and an antenna.
  3. Download the matching SD-card image and write it to an SD card.
  4. Boot your SBC and wait — usually a few minutes, but in some cases 15 to 20 minutes depending on the model and image.

If you jump to the browser too early, the feeder may simply not be up yet. Give it the full wait window on slower boards before concluding something is wrong.

Quick decision table

Situation What to use
Wired Ethernet, mDNS working http://adsb-feeder.local
mDNS not working on your network http://my.adsb.im
WiFi not configured on the card Connect to adsb.im-feeder hotspot, then browse

Common sticking points

  • Nothing loads at adsb-feeder.local: this is usually an mDNS issue on the home network, not a dead feeder. Switch to my.adsb.im.
  • You never set up WiFi: don't wait for a network connection that won't appear — connect to the adsb.im-feeder hotspot instead.
  • You checked too soon: first boot can take 15 to 20 minutes on some models. Wait before troubleshooting.
  • No dongle or antenna attached: the hardware steps come before access; a feeder without its SDR and antenna isn't the setup you're trying to reach.

Once you're in, the feeder plots aircraft on your own map and can share to aggregators such as adsb.lol, ADS-B Exchange, FlightAware, FlightRadar24, and OpenSky Network, among others.

What Hardware and Steps Are Needed to Set Up an ADSB.im Feeder?

To set up an ADSB.im feeder you need three pieces of hardware — a supported single board computer (SBC), an SDR radio dongle, and an antenna — then you download the matching SD-card image, write it to a card, boot the board, and open the feeder's web interface. The SBC image route is the recommended starting point because it is the most tested and typically the easiest to use, with the fewest pitfalls.

Hardware you need

Item Notes
Supported single board computer Raspberry Pi is the most common choice, and several other boards are supported
SDR radio dongle Receives the radio signals
Antenna Connects to the SDR dongle

The same Feeder Image also supports AIS (ships), Sonde (weather balloons), and ACARS/VDL2/HFDL (aircraft-to-ground data), so the hardware you attach determines what you track.

Installation steps (SBC image — easiest)

  1. Start with one of the supported single board computers.
  2. Add an SDR radio dongle and an antenna.
  3. Download the SD-card image that matches your board and write it to an SD card.
  4. Boot the SBC and wait. Depending on the model and the specific image this usually takes a few minutes, but in some cases it can take 15 to 20 minutes.
  5. If you have wired Ethernet — or after you have configured WiFi — go to http://adsb-feeder.local. If mDNS is not working on your home network, go to my.adsb.im, which should redirect you to your new ADS-B feeder.

If you plan to use WiFi

If you could not configure WiFi while writing the SD card, the image creates a WiFi hotspot named adsb.im-feeder that you can connect to in order to finish setup.

Other installation routes

Besides the SBC image, the site lists two alternatives:

  • DietPi — described as easy.
  • Linux — described as more advanced.

When in doubt, the SBC image should be your first choice.

What you get once it is running

Your feeder plots aircraft on your own map, showing recent tracks and information such as altitude, speed, and — for many commercial flights — the flight route. You can also share your data with aggregators including adsb.lol, adsb.fi, ADS-B Exchange, FlightAware, FlightRadar24, OpenSky Network, Plane.watch, Plane Finder, and others.

Which ADSB.im Installation Method Should I Choose?

Choose the Single Board Computer (SBC) image unless you have a specific reason not to. ADSB.im's own documentation calls it the first choice: it is the most tested, typically the easiest to use, and has the fewest pitfalls. Pick DietPi if you want a lighter, more managed Linux base on supported hardware, and pick the plain Linux route only if you are comfortable administering a system yourself or need to run the feeder on hardware the images don't cover.

The three methods at a glance

Method Best for Effort What you manage
Single Board Computer image Most people, first-time feeders Lowest Almost nothing; flash and boot
DietPi Users who want a lean OS with a menu-driven setup Low to moderate Some OS-level choices
Linux Advanced users, non-standard hardware, existing servers Highest The whole stack

All three end up running the same ADS-B Feeder Image software, so the difference is in setup and maintenance, not in what the feeder can receive.

Single Board Computer image (easiest)

This is the path ADSB.im tests most and recommends when you are unsure.

  1. Start with one of the supported single board computers. Most people use a Raspberry Pi; several other boards are supported.
  2. Add an SDR radio dongle and an antenna.
  3. Download the matching SD-card image and write it to an SD card.
  4. Boot the SBC and wait. Depending on the model and image this usually takes a few minutes, but in some cases 15 to 20 minutes.
  5. If you have wired Ethernet, or once you have configured WiFi, open http://adsb-feeder.local. If mDNS does not work on your network, use my.adsb.im, which redirects to your new feeder.

Expected result: a running feeder reachable from a browser on your local network, ready to plot aircraft on your own map and share to aggregators.

Common snag: if you planned to use WiFi and could not configure it while writing the SD card, the image creates a WiFi hotspot named adsb.im-feeder that you connect to in order to finish setup.

DietPi (easy)

Choose this when you want a smaller, more controlled operating system underneath the feeder and are willing to make a few more decisions during setup. It sits between the fully prebuilt SBC image and a manual Linux install: less hand-holding than the image, far less work than building the stack yourself. It still assumes supported hardware and an SDR dongle plus antenna.

Linux (more advanced)

Choose this if you are already running a Linux machine you want to reuse, if your hardware is not covered by the supported board list, or if you want full control over updates and services. You take on the operating system, dependencies, and ongoing maintenance yourself. If you are new to ADS-B feeding, this is the option most likely to cost you an evening of troubleshooting.

What the feeder can receive

The image is not limited to aircraft. Beyond ADS-B it supports AIS for tracking ships, Sonde for weather balloons, and ACARS/VDL2/HFDL for data transmissions from aircraft to ground stations. Each area has its own aggregators and communities, but the setup approach is the same across them.

You can plot aircraft on your own map and share to aggregators including adsb.lol, Fly Italy Adsb, TheAirTraffic, adsb.fi, sdrmap, 1090MHz UK, ADS-B Exchange, ADSBHub, HPRadar, airplanes.live, AVDelphi, FlightAware, FlightRadar24, OpenSky Network, Plane.watch, Plane Finder, Planespotters.net, AirNav Radar, Radar Virtuel, and more.

How to decide

  • You just want it working this weekend: SBC image.
  • You want a leaner OS and don't mind a menu-driven setup: DietPi.
  • You have spare Linux hardware, unusual hardware, or want full control: Linux.
  • You are unsure: the SBC image, per ADSB.im's own guidance.

The hardware requirements are the same in every case: a supported board or Linux host, an SDR radio dongle, and an antenna.

What Is ADSB.im?

ADSB.im is the home of the ADS-B Feeder Image, a ready-made software image that turns your own hardware into a receiver for aircraft, ship, and weather-balloon signals. It is aimed at people who want to plot nearby traffic on their own map and share that data with public aggregators, without assembling a feeder stack by hand. The easiest path is a single-board computer (SBC) image, which the project describes as the most tested and least error-prone option.

What the Feeder Image actually does

The image started as a simpler way to set up an ADS-B feeder, and has since grown to cover several signal types:

  • ADS-B — track aircraft, see recent tracks, altitude, speed, and for many commercial flights even the flight route.
  • AIS — track ships.
  • Sonde — track weather balloons.
  • ACARS / VDL2 / HFDL — receive data transmissions from aircraft to ground stations.

Each of these areas has its own aggregators and communities, but they share the same setup approach through the Feeder Image.

Sharing your data with aggregators

One of the main reasons to run a feeder is to contribute to public networks. ADSB.im lists a long set of supported aggregators you can feed, including adsb.lol, Fly Italy Adsb, TheAirTraffic, adsb.fi, sdrmap, 1090MHz UK, ADS-B Exchange, ADSBHub, HPRadar, airplanes.live, AVDelphi, FlightAware, FlightRadar24, OpenSky Network, Plane.watch, Plane Finder, Planespotters.net, AirNav Radar, Radar Virtuel, and more.

You can plot aircraft on your own map first, then forward the same data outward.

Installation options

There are several ways to install the ADS-B Feeder Image, depending on where and how you want to run things. When in doubt, the project recommends starting with an SBC image.

Method Difficulty Notes
Single Board Computer image Easiest Most tested, fewest pitfalls
DietPi Easy Alternative install path
Linux More advanced For users comfortable with a full Linux setup

Most people appear to use Raspberry Pis, though several other boards are supported.

Step-by-step: SBC image install

  1. Start with one of the supported single board computers.
  2. Add an SDR radio dongle and an antenna.
  3. Download the matching SD-card image and write it to an SD card.
  4. Boot your SBC and wait. Depending on the model and specific image this usually takes a few minutes, but in some cases it can take 15 to 20 minutes.
  5. If you have wired Ethernet, or after you have configured WiFi, go to http://adsb-feeder.local. If mDNS isn't working on your home network, use my.adsb.im, which should redirect you to your new ADS-B feeder.

If you plan to use WiFi

If you weren't able to configure WiFi while writing the SD card, the image creates a WiFi hotspot named adsb.im-feeder that you can connect to in order to finish setup.

What you need before starting

  • A supported single-board computer.
  • An SDR radio dongle.
  • An antenna.
  • An SD card to write the image to.
  • A wired Ethernet connection, or a way to join the adsb.im-feeder hotspot to configure WiFi.

Common sticking points

  • mDNS not resolving. adsb-feeder.local depends on mDNS working on your network. If it doesn't, fall back to my.adsb.im.
  • First boot taking a while. Don't assume something is broken if the initial boot runs long; 15 to 20 minutes is within the expected range for some models and images.
  • WiFi not pre-configured. You can still recover by connecting to the adsb.im-feeder hotspot the image creates.

If your goal is simply to get an aircraft-tracking feeder running with minimal fiddling, the SBC image is the intended starting point. If you want to run it inside an existing Linux environment, that path exists but is described as more advanced.

What Signals Can ADSB.im Receive Besides Aircraft?

ADSB.im is not limited to aircraft tracking. According to the project's own description, the ADS-B Feeder Image has expanded beyond its original ADS-B purpose to also support AIS (ship tracking), Sonde (weather balloon tracking), and ACARS/VDL2/HFDL (data transmissions between aircraft and ground stations). Each of these areas has its own aggregators and communities, but they share the same setup approach through the Feeder Image.

The Four Signal Types ADSB.im Handles

Signal type What it tracks/receives Typical use
ADS-B Aircraft positions, altitude, speed, flight routes Feeding aircraft tracking aggregators
AIS Ships Vessel tracking
Sonde Weather balloons Radiosonde tracking
ACARS / VDL2 / HFDL Data transmissions from aircraft to ground stations Aircraft-to-ground communications

The project describes itself as "the easiest way to track nearby aircraft, ships, or even weather balloons with your own hardware and share with others." So the scope is deliberately broader than plane spotting alone.

What Each Non-Aircraft Signal Gives You

AIS — Ship Tracking

AIS lets you plot vessels on your own map rather than only aircraft. If you live near a coast, a harbor, or a busy shipping lane, this is the reason to add AIS to your feeder. The same hardware-and-image workflow applies; you are just decoding a different signal.

Sonde — Weather Balloons

Sonde tracking follows weather balloons (radiosondes) as they ascend and drift. This is a niche but active community. It is useful if you want to follow launches in your region and contribute that data, and it runs on the same Feeder Image rather than a separate system.

ACARS / VDL2 / HFDL — Aircraft-to-Ground Data

These are data transmissions sent between aircraft and ground stations, not position broadcasts. Receiving them gives you a different view of aviation activity than ADS-B position data. As with AIS and Sonde, the project notes each area has its own aggregators and communities.

Sharing Your Data

ADSB.im is built around feeding aggregators. The project lists many aircraft-focused destinations, including adsb.lol, Fly Italy Adsb, TheAirTraffic, adsb.fi, sdrmap, 1090MHz UK, ADS-B Exchange, ADSBHub, HPRadar, airplanes.live, AVDelphi, FlightAware, FlightRadar24, OpenSky Network, Plane.watch, Plane Finder, Planespotters.net, AirNav Radar, and Radar Virtuel, among others. The non-aircraft modes (AIS, Sonde, ACARS/VDL2/HFDL) have their own aggregators and communities, which you would select based on which signal you are decoding.

What You Need to Get Started

The setup path is the same regardless of which signal you choose:

  1. Start with one of the supported single board computers (Raspberry Pi is the most common; several other boards are supported).
  2. Add an SDR radio dongle and an antenna.
  3. Download the matching SD-card image and write it to an SD card.
  4. Boot the SBC and wait — usually a few minutes, though some models and images can take 15 to 20 minutes.
  5. With wired Ethernet, or after configuring WiFi, go to http://adsb-feeder.local, or use my.adsb.im if mDNS is not working on your network, which redirects to your new feeder.
  6. If you could not configure WiFi while writing the SD card, the image creates a WiFi hotspot named adsb.im-feeder that you connect to.

The project recommends the Single Board Computer image as the first choice when in doubt, since it is tested the most, is typically easiest to use, and has the fewest pitfalls. DietPi is described as easy, and a plain Linux install as more advanced.

How to Decide Which Signals to Receive

  • Already running an ADS-B feeder and want more? Add AIS if you are near water, or Sonde if you want to follow weather balloon launches.
  • Interested in aviation communications rather than positions? ACARS/VDL2/HFDL is the relevant mode.
  • Just want the simplest start? Begin with the standard ADS-B setup on a supported SBC, then expand to the other signal types once the feeder is running.

Because all four signal types run through the same Feeder Image and the same hardware-and-boot workflow, the choice is mainly about which antenna, dongle, and aggregator match the signal you care about — not about learning a separate installation process for each one.

Website Overview

The available information shows a mix of normal operation and configuration gaps. Depending on how the website is used, these gaps may affect secure access or the consistency of its public presentation.

Domain and Registration

The domain uses the common .im extension, which is not an independent safety signal.

DNS and Email

Nameservers are provided by name.com, indicating managed DNS hosting. MX records point to the subsurface-divelog.org email service. No CNAME was found; the observed records resolve directly to addresses. SPF and DMARC are configured. DKIM status is unknown. The lowest observed DNS TTL is 300 seconds.

TLS and Certificates

The public key uses EC with 256 bits. The server supplied a complete certificate chain. No organization name is present in the certificate; the available fields are consistent with domain validation. The certificate was issued by Let's Encrypt, commonly associated with automated certificate services. The certificate's total validity is about 89 days, consistent with a short renewal cycle.

HTTP and Browser Security

The checked browser-security headers were not detected, leaving fewer explicit browser-side safeguards. No X-Powered-By header was found, reducing one common source of backend fingerprinting information. No obvious internal addresses or debug information were found in the headers. The Server header contains the custom value uvicorn. No explicit CDN or WAF marker was found in the response headers.

Technology Stack Analysis

The public page identifies Bootstrap without precise versions, leaving fewer clues for version-specific scanning.

Search and Social Sharing

No homepage canonical URL was detected. If duplicate URLs exist, consolidation may be less explicit. The title has 7 characters, within a common display range. A meta description is present, with 49 characters. The observed directives allow indexing and link following. No Generator meta tag is publicly exposed.

Hosting and Email

DNSname.com
HostingHostHatch, LLC
Emailsubsurface-divelog.org
Approximate IP geolocation (inferred; a CDN or proxy may differ from the origin server) United States flagLos Angeles, California, United States Inferred 31.220.30.207

Registration details

RDAP / WHOIS

RegistrarUnknown
RegisteredUnknown
ExpiresUnknown
Domain statusUnknown
Nameserversns1.name.com、ns2.name.com、ns3.name.com、ns4.name.com
DNSSECunknown

DNS records

DNS

TypeNameValueTTLPriority
Aadsb.im31.220.30.207300—
MXadsb.immailman.subsurface-divelog.org30010
MXadsb.imbackupmx.gr8dns.org300100
NSadsb.imns1.name.com300—
NSadsb.imns2.name.com300—
NSadsb.imns3.name.com300—
NSadsb.imns4.name.com300—
TXTadsb.imopenpgp4fpr:966fa5982c8e073ec2d45f5599151bc196a1b6bb300—
TXTadsb.imv=spf1 mx a:mx.hohndel.org a -all300—
DMARC_dmarc.adsb.imv=DMARC1;p=quarantine;pct=100;rua=mailto:[email protected];ruf=mailto:[email protected];ri=300;aspf=s;adkim=s;fo=1300—

TLS and certificates

TLS / SSL

AssessmentNormal configuration
Supported protocolsTLSv1.2、TLSv1.3
Negotiated protocolTLSv1.3
Certificate subjectmy.adsb.im
IssuerLet's Encrypt
Valid until2026-11-03T10:56 · Remaining when checked: 32 days
Verification detailsCertificate trust: Passed · Hostname match: Passed

HTTP response headers

HTTP

HeaderValue
content-typetext/html; charset=utf-8
serveruvicorn

Identified technologies

Bootstrap

Pages, Search and Sharing

User reviews (0)

  • No reviews yet.