Run your domains, DNS and certificates from one place
One connection for your whole Openprovider portfolio: domains, DNS and certificate expiry together
Connect Openprovider once to manage domains, DNS and certificates without switching panels.
- Domains: see renewal dates, nameservers and lock state for your whole portfolio, and register, renew, transfer in or change settings without opening the Openprovider panel.
- DNS: manage zones and records for any domain, whoever it's registered with — existing zones are found and imported automatically when you connect, and edits made in InfraNest are sent straight to Openprovider.
- Certificates: your Openprovider certificates appear in your certificate inventory with their expiry dates, next to certificates from every other provider you connect.
- Spend and labels: see what your domains, DNS and certificates cost in one place, and tag resources so one label works across every provider you use.
What it looks like in InfraNest
What you can do
Once OpenProvider is connected, this is what InfraNest can do with it.
- Whole domain portfolio imported on connect
- DNS zones for any domain, found automatically
- Record edits sent straight to Openprovider
- Certificate expiry tracked alongside domains and DNS
- Spend across every connected provider in one place
Not supported
This integration doesn't manage cloud resources — that stays with whatever provider you use for that. Changing a domain's owner also isn't handled here, since Openprovider treats that as a paid, separately-confirmed transfer; do that directly in the Openprovider panel.
How to connect it
- 1
Open the Openprovider integration
Go to Integrations and select Openprovider.
- 2
Label the account
Give the connection an Account label so you can tell it apart from others, especially if you manage more than one Openprovider account.
- 3
Enter the API credentials and connect
Enter the API username and password for the dedicated user you set up, then select Connect — InfraNest checks the credentials and starts importing your domains.
That’s it — OpenProvider is connected.
Full setup guideSet up with AI
I use OpenProvider, and I want to connect it to InfraNest (infranest.io) — it manages domains, DNS, servers and certificates across providers. InfraNest asks for: API username and password. Walk me through creating that in OpenProvider: where each setting is in the current interface, whether a read-only option exists, and how to check it works before I paste it in.
What syncs
What InfraNest keeps in sync with OpenProvider.
| DNS zones | DNS zones and records |
| Domains | Domains, expiry dates, nameservers and lock state |
| Certificates | Certificates and their expiry |
MCP server
OpenProvider in Claude and ChatGPT
Connect your AI assistant to InfraNest and ask about your OpenProvider account in plain words, next to every other provider you use. It reads, and acts only when you allow it.
- Which of my OpenProvider domains expire in the next 60 days?
- Where does shop.example.com point, and did anything change there this week?
- Which certificates expire this month, and does anything renew them?
Questions
#Can I use this for just DNS, without moving my domains to Openprovider?
Yes. DNS zones can be hosted here for any domain, no matter where it's registered, so you can use Openprovider as your DNS layer without transferring domains to it.
#What happens if the Openprovider credentials are revoked or expire?
InfraNest will report that authentication is failing and pause the affected features until you update the credentials. Your existing domain, DNS and certificate data isn't lost, but changes stop going through until the connection is working again.
#Can InfraNest actually change things in my Openprovider account, or is this read-only?
It can make changes. DNS record edits, nameserver changes, DNSSEC, transfer lock, WHOIS privacy, auto-renew, and actions like registering, renewing or transferring a domain are all sent to Openprovider from InfraNest.
#Will I know before a domain or certificate expires?
InfraNest tracks domain renewal dates and certificate expiry and can trigger alerts and automations when something is expiring, expired, or when a certificate changes unexpectedly.
#What do I need before connecting Openprovider?
A dedicated Openprovider user with API access switched on, no two-factor authentication set on it, and InfraNest's IP address allowed — see the setup guide.
#Is there a OpenProvider MCP server?
Yes, through InfraNest. Once OpenProvider is connected, InfraNest’s MCP server lets Claude, ChatGPT, Cursor, VS Code and other assistants read your domains, DNS records and certificates at OpenProvider, together with every other provider you use. It works on every plan, including Free.
One dashboard for every provider
Add this integration, then the rest of your stack — domains, DNS, servers, certificates and monitoring in one place.
Free plan · No credit card required · Set up in minutes