Name.com

Cyber and operational findings

Analyst-reviewed records. The grade states how well the cause is established; event, first public observation and acknowledgement are separate dates.

No public findings for this organisation.

Provider status posts

Collected from the organisation's own public status page. These are its words; DFX adds only the wording classification.

• Incident Root Cause Analysis: Oct 31, 2026 DNS ChangesNov 3 20:33 UTC · monitoring
  Provider used security languageCredential or token reset requestedRestoration reported
  1. Nov 3 20:33 UTC monitoring: On Oct 31, 2026 (UTC), unauthorized DNS changes were made to 15 customer domains. All changes were restored by Oct 31, 16:11 UTC, and system access for the account where the changes originated has been fully revoked. Read the full incident report here:...
  View on the provider's status page
• Degraded Performance - .si Registry ConnectionOct 1 15:20 UTC · resolved
  Service restricted or degradedRestoration reported
  1. Oct 1 15:20 UTC investigating: We are currently experiencing degraded performance for .si domain operations due to significant latency at the .si registry. Registration, renewal, transfer, and update requests for .si domains may take considerably longer than usual to complete, and some requests may time out....
  2. Nov 3 17:26 UTC monitoring: The .si registry has made updates to their EPP servers and we will continue to monitor these connections.
  3. Nov 3 17:47 UTC monitoring: We are continuing to monitor for any further issues.
  4. Nov 3 17:49 UTC resolved: This incident has been resolved.
  View on the provider's status page
• Service degradation (api.name.com, www.name.com)Jul 24 13:04 UTC · resolved
  Restoration reported
  1. Jul 24 13:04 UTC monitoring: Due to service provider issues, name.com started experiencing performance degradation at 4:57am MDT, affecting customers of api.name.com and www.name.com. Recovery started at 5:09 am MDT, with services fully restored at 5:12 am MDT. We are continuing to monitor activity until...
  2. Jul 24 13:09 UTC resolved: This incident has been resolved.
  View on the provider's status page
• Identity Digital - Domain Create and Renewal ErrorsJul 11 19:00 UTC · resolved · minor impact
  Restoration reported
  1. Jul 11 20:21 UTC resolved: Between 1:01 PM and 1:19 PM MT (19:01–19:19 UTC), we were experiencing errors on registrations and renewals for TLDs operated by Identity Digital. The issue has been resolved, and registrations and renewals are now processing normally. We apologize for any inconvenience this...
  View on the provider's status page
• DENIC DNS Disruption - DNSSEC outage .DEMay 5 22:01 UTC · resolved · major impact
  Service restricted or degradedInvestigation mentionedRestoration reported
  1. May 5 22:01 UTC investigating: DENIC is currently experiencing a disruption in its DNS service for .de domains. As a result, all DNSSEC-signed .de domains are currently affected in their reachability. The root cause of the disruption has not yet been fully identified by DENIC. DENIC’s technical teams are...
  2. May 6 00:07 UTC resolved: This incident has been resolved. DENIC confirmed systems are operating normally again for .de domains, but are still investigating the cause of the temporary disruption. For a posted summary directly from DENIC, follow their status page here https://status.denic.de/.
  View on the provider's status page
• API outageApr 29 15:03 UTC · postmortem · critical impact
  Service restricted or degradedInvestigation mentionedRestoration reported
  1. Apr 29 15:03 UTC investigating: We're currently investigating the issue.
  2. Apr 29 16:22 UTC monitoring: After further remediation, we are seeing recovery.  We are still monitoring closely to ensure its sustained.
  3. Apr 29 16:32 UTC resolved: This incident has been resolved.
  4. May 8 15:29 UTC postmortem: * **Duration:** 14:33 UTC – 16:09 UTC \(~96 minutes\) * **Impact:** The [api.name.com](http://api.name.com) endpoint was unreachable to external clients, resulting in socket timeouts and 502 errors. * **Root Cause Summary:** The outage was triggered by an unanticipated 50x surge...
  View on the provider's status page
• Website and API OutageNov 18 15:43 UTC · resolved · major impact
  Service restricted or degradedRestoration reported
  1. Nov 18 15:43 UTC resolved: After an interruption to www.name.com and api.name.com, service was restored at approximately 2:22pm UTC. We are continuing to monitor to ensure continued stability.
  View on the provider's status page
• .Space DNS resolution degradedSep 24 15:32 UTC · resolved · maintenance impact
  Service restricted or degradedRestoration reported
  1. Sep 24 15:32 UTC monitoring: The registry operator for .space has encountered degraded DNS resolution on .space domains. We will update as soon as we receive another update from the .space registry with updates
  2. Sep 25 16:06 UTC resolved: This incident has been resolved.
  View on the provider's status page

Documented dependents

Organisations publicly documented as relying on this provider. A relationship is not an impact.