Data sources
Every external service Asterion talks to, what it sends there, and how to switch it off.
Asterion’s own data comes from the satellites. A few public services add context. None of them gets data about users.
| Service | Asked by | Sends | Used for | Switch |
|---|---|---|---|---|
| crt.sh | Polaris | monitored domain names | Certificate Transparency: new certificates and subdomains | POLARIS_CT_ENABLED, plan parameter ct_lookup |
| RIPEstat | Polaris | public IP addresses (of hosts, and the address a satellite connects from) | announced prefix, origin AS, approximate location of hosts and satellites | POLARIS_RIR_ENABLED |
| RDAP of the RIRs (RIPE NCC, ARIN, APNIC, LACNIC, AFRINIC) | Polaris | public IPs, AS numbers | registration data, abuse contacts | POLARIS_RIR_ENABLED |
| Public Suffix List | — (shipped with Polaris) | nothing | registered domain of a hostname | — |
| Registry name servers | Polaris | new domain and hostname | does a new domain / hostname exist | POLARIS_VERIFY_DOMAINS, POLARIS_VERIFY_HOSTNAMES |
| Nominatim or Photon (or own server) | Polaris, on click | the address typed into a location form | coordinates for the maps | System settings → Address lookup |
| ntfy, SMTP servers | Polaris (queue) | notification title and text | notifications | per channel; internal servers only when a super admin allows them |
| Probe hosts for IPv4/IPv6 | each Pulsar | a TCP connection | can the satellite reach IPv4 / IPv6 | — |
| Your targets | each Pulsar | scans and protocol handshakes | everything else | your plans |
Satellites ask no geolocation service: Polaris locates them from the address they connect from and tells them what it sees.
The maps are drawn from a world map that ships with Polaris; the browser loads nothing from other hosts. Polaris itself loads no fonts, scripts or styles from anywhere (strict Content-Security-Policy).