What happened?

Domainr verifies domain status by connecting directly to registries. Following a routine certificate rotation, the new certificate no longer includes the client authentication component that some registries require to accept these connections. This reflects a public certificate authority (CA) change that took place earlier this year.

For the affected TLDs, Domainr can't verify status directly with the registry. It falls back to resellers, DNS, or WHOIS where available. In situations where none are available, the API returns an "unknown" or “non-authoritative” status.

The API continues to operate normally and returns successful (200) responses. Domain status data for affected TLDs may be less accurate or incomplete.

What’s next? What do I have to do?

There is no workaround, and no action is required on your part. Our Engineering team has already reached out to affected registries to partner with them on supporting and installing compatible certificates. Resolution depends on both this partnership and the completion of necessary system updates by the affected registries. Fastly Support is available to answer questions you may have and provide updates if available.

We sincerely apologize for not providing earlier notice. We will update this status page as we receive more information. 

Customers with any other questions or concerns may engage with our Support team through https://support.fastly.com or by contacting your designated account management team members.