WordPress plugin (Connect)

The WordPress plugin uses Connect for optional outside protection. End-user install steps: Docs -> WordPress plugin.

WordPress.org: Aepto Domain Expiry, SSL & DNS Monitor

Behavior for integrators

Domain Anchor runs entirely on the WordPress host for free (RDAP/DNS/TLS/tether/mail). No Aepto token required.
Connect stores OAuth tokens on the site and calls Aepto for outside uptime, portfolio, Watch, Theft Guard, and Attention.
Connect requires a public HTTPS site. Local http:// / Docker callbacks are rejected by design.
Users disconnect from Aepto -> Settings -> Disconnect & revoke tokens or from Connected apps.

Do not ask WordPress admins to paste aep_live_ keys into the plugin. Connect is the supported auth path for the first-party plugin.

Does Domain Anchor need an Aepto token?

No. Anchor runs on the WordPress host for free (RDAP/DNS/TLS/tether/mail) without Connect.

Why does Connect fail on localhost?

Connect requires a public HTTPS site. Local http:// / Docker callbacks are rejected by design.

Should admins paste aep_live_ keys into the plugin?

No. Connect is the supported auth path for the first-party plugin.

Where are end-user install steps?

Docs → WordPress plugin (WordPress.org listing, Anchor, and Connect).