Choose a host and connect your updater
Select one of your dashboard hosts below, then approve. The installer will be configured for that host.
Approve only if you started setup on a device you trust. Match this code to the one shown by your installer:
Connecting replaces this host’s current token. Other updaters using its old token will stop working. The installer receives the new token automatically.
Verify your email
Check your inbox to activate hostname management. Verification links expire after 24 hours.
Create a hostname
You'll receive its updater token immediately after creating it. This menu shows the domains available to your account. ipalive.link is available to everyone. Premium accounts can also choose ipanchor.link, hostperch.link, ipsteady.link, or hostalive.link. During setup, enter the short host name and choose its domain from the numbered menu.
Your updater token
Copy this token now. It is shown only when created or replaced. If you lose it, generate a new one from your hostname's Manage controls.
Use the platform setup instructions below. Each hostname has its own token; this token cannot configure a different hostname.
Return here to confirm your first update and public IP address.
NETWORK CONTROL
Your hostnames
| Hostname | Addresses | DNS check-in | Updater software | Manage |
|---|
Installed updaters check for signed software fixes once a day. Updates preserve your hostname, token, and settings. If a release check fails, DNS updates continue using the installed release.
Set up your updater
Choose the platform of the device on the network you want to update. It may differ from the device you’re browsing on.
Download installerManage Windows hosts without reinstalling
Use Windows PowerShell 5.1 as Administrator. New installs include the ipalive command and daily signed software updates. Existing users download the latest package once, review and unblock its scripts if Windows blocks them, then run this in its windows folder:
powershell.exe -NoProfile -File .\setup-command.ps1
Run ipalive repair YOURHOST once for each existing host to enable automatic updates. Reopen your Administrator terminal if needed, then use:
ipalive list ipalive add router ipalive update router ipalive repair router ipalive logs router ipalive remove router ipalive upgrade
Update prompts for a replacement token. Repair validates the saved token and recreates the boot task. Remove stops the local task and removes its local credential; your dashboard host and DNS records are retained.
Manage Linux hosts without reinstalling
Run without sudo. New installs include the ipalive command and daily signed software updates. Existing users download the latest package once and run this in its linux folder:
python3 setup-command.py export PATH="$HOME/.local/bin:$PATH"
Add ~/.local/bin to your shell’s PATH permanently if needed. Run ipalive repair YOURHOST once for each existing host to enable automatic updates, then use:
ipalive list ipalive add router ipalive update router ipalive repair router ipalive logs router ipalive remove router ipalive upgrade
Update prompts for a replacement token. Repair validates the saved token and reloads the timer. Remove stops the local updater and removes its credential; your dashboard host and DNS records are retained. Enable user lingering as instructed during installation for updates after logout and reboot.
Manage your Mac hosts without reinstalling
System installation includes the ipalive command. Updaters check for signed fixes daily; ipalive upgrade checks immediately. For an existing installation, download the latest package once and run sudo python3 setup-command.py from its mac folder. After installing the command, run ipalive repair YOURHOST once for each existing host to enable automatic software updates.
ipalive list ipalive add router ipalive update router ipalive repair router ipalive logs router ipalive remove router ipalive upgrade
Add configures a dashboard host; update asks for its replacement token; repair reloads its service using saved settings. Remove stops only that local updater and removes its credential. Your dashboard host and DNS records are retained. Revoke its token in the dashboard to invalidate other copies.
Run setup on the target device, enter the selected host name, and paste its own token. Setup validates the pair before installation. If you no longer have its token, choose Generate new token above; that replaces its previous token.
Software version/status is reported by the updater; missing or delayed reports do not prove the device is offline. Older updaters show Version not reported until upgraded. Your updater runs every five minutes while its device is awake. If a name is not configured in your dashboard, create it first. Names already registered to another account cannot be claimed. Another hostname’s token is rejected.
SERVICE OPERATIONS
Admin overview
Service totals
Needs attention
Current host and service issues. Select an item to investigate.
Shared across admins. Issues return when snoozes expire or conditions worsen. Health cards still show the underlying problems.
Acknowledged or snoozed
Service health
Health notes, email usage and account activity
Past error events (24 hours)
Hosts needing attention
| Host | Account | Problem |
|---|
No hosts currently need attention.
Webhook delivery failures
Verified, active admins receive one email per account and webhook configuration after three unsuccessful attempts or a final failure. Further failures stay quiet until every outstanding delivery for that configuration clears. Email allowance may delay alerts.
Failed deliveries and retries after a failed attempt from the last 30 days. Select the account or host to investigate. Delivered and cancelled events are excluded. Connection tests have no host. Retry now sends an eligible delivery immediately on the user’s behalf and records the admin action. The owning account’s limits and endpoint safety checks still apply. Viewing older pages pauses automatic list refresh; use Refresh webhook failures to return to the latest records.
| Created / event | Account | Host | Status / attempts | Error / next retry | Action |
|---|
User accounts
| Account | Access | Hosts / Sessions | Manage |
|---|
Revoking premium prevents new premium-domain hosts and new connections to them; existing hosts and DNS remain. Suspension blocks sign-in and updater requests while retaining DNS. Owner and administrator accounts are protected.
Scheduler and email usage
Hostname domains and DNS access
Check the Worker’s DNS token access after changing its zone permissions.
Updater fleet
| Hostname | Account | Updater software |
|---|
Abuse controls
Suspension is available in account details. Reservations apply to new hosts across all service domains; existing hosts are retained.
Search audit history
| Time | Event | Host | Details |
|---|
Recent activity
| Time | Event | Host ID | Details |
|---|
Details
Support reports include account and host diagnostics. They exclude passwords, tokens, session identifiers and provider secrets. Share only with trusted support.
Host notifications
Missing check-ins indicate updater inactivity, not device reachability. We check hourly; emails may arrive up to an hour after your chosen threshold. Hostnames and DNS records are retained.
Free accounts receive alerts after 24 hours, then weekly. Configurable alerts and recovery emails are Premium features.
PREMIUM INTEGRATIONS
Webhooks & delivery status
Send signed JSON events to your public HTTPS receiver. Choose IP changes, missing check-ins and recovery independently of email preferences. Your inactivity threshold and reminder interval apply to webhooks too.
No webhook configured.
Save this key in your receiver’s secret settings. It verifies deliveries; it cannot update your hosts.
Delivery and signature guide
Events use ip.changed, host.missing, host.recovered or test. The initial IP assignment and unchanged check-ins do not send IP-change notifications.
Verify X-IPAlive-Signature as v1=HMAC-SHA256(signing key, timestamp + "." + raw request body), using the timestamp from X-IPAlive-Timestamp. Use a constant-time comparison and reject timestamps more than five minutes old. Deduplicate X-IPAlive-Event-ID; retries reuse the event ID.
Your receiver must accept JSON and return HTTP 2xx. Redirects and private network addresses are blocked. Email notifications use our shared sending allowance. Webhooks allow 100 delivery attempts per account per UTC day. Failed deliveries retry up to six total attempts, with retries checked every five minutes; events expire after 24 hours. Settings changes cancel queued webhook deliveries. Use Retry now after fixing your receiver to send a failed or waiting retry immediately. Manual retries are limited to once per minute per delivery and keep the original event ID; expired events and changed webhook settings require a new test. Logs are retained for 30 days.
Recent IP-change emails and webhook deliveries
| Created | Channel / event | Status | Attempts / result | Action |
|---|
IP-change history
Confirmed DNS address changes from the last 90 days. History starts when this feature is enabled; unchanged check-ins do not add entries.
| Time | Address family | Previous address | New address |
|---|
Account sign-in
You can add or change your password here. Google sign-in remains optional.
IPAlive on your home screen
Install this dashboard as an app from your browser’s menu. On iPhone or iPad, open it in Safari, tap Share, then Add to Home Screen. The app manages your account; install your device’s updater separately.