Only your networks can open HQ
YesHQ refuses any address outside its private ranges.
| Connection | Reads | Reaches | State | |
|---|---|---|---|---|
| Infrastructure 5 | ||||
example-npm
https://proxy.example.com
Reads nothing, 6 never read
|
|
– | Not answering 1 problem | |
example-dns
https://api.example.com/client/v4
Reads nothing, 2 never read
|
|
example.com · example.net | Working | |
a-portainer
https://portainer.example.com
Reads 1 thing, 6 never read · just now
|
|
app-host · another-host | Working | |
Public DNS resolver
https://dns-lookup.com
|
|
– | Set up | Look up a name Look up an address |
Public address registry
https://rdap.org
|
|
– | Set up | Look up an address |
| Dashboard 1 | ||||
National Weather Service
https://api.weather.gov
|
|
Dashboard weather | Set up | – |
HQ cannot work out the path to its own name.
HQ refuses any address outside its private ranges.
HQ has no reading of the tailnet policy.
This request did not arrive over TLS.
This request came straight to HQ.
HQ keeps no secret itself. Each connection names the place that keeps its secret.
HQ cannot confirm these credentials are limited to what it needs. Full account access: a-portainer, example-npm.
3 connections have no reading.
HQ has no reading of an access list for this name.
How I am connected