.dk logo

Is .dk Down?

SaaSLive status, outages, and incident history

No. .dk is up right now.

Every monitored .dk system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · 60s while moving

Know the moment .dk breaks

.dk is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

Official .dk status page
How we know: the official .dk status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

.dk Component Status

The main .dk systems on this page. All 19 are operational right now.

19operational
Administrative services
Operational
DAS
Operational
DNS (.dk) » a.nic.dk
Operational

16 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking DNS (.dk) » b.nic.dk, DNS (.dk) » c.nic.dk, DNS (.dk) » d.nic.dk, DNS (.dk) » l.nic.dk, DNS (.dk) » p.nic.dk, DNS (.dk) » s.nic.dk, EPP, Registrar Portal, Sandbox environment, Self-Service Portal, Stats, Website, and 3 more.

See all of them free

Component statuses may change independently during partial outages.

Recent .dk Outages & Incidents

Incident history from the official .dk status page, including resolution updates.

Punktum dk Releases Self-Service Portal Version 6.15.0Scheduled for Sep 24, 2026 · 1h 0mScheduled

Verification is currently underway for the maintenance items. --- [2026-09-24T10:00:09.373+02:00] (in_progress) Scheduled maintenance is currently in progress. We will provide updates as necessary. --- [2026-09-24T09:32:32.898+02:00] (scheduled) Punktum dk is releasing a new version of the Self-Service Portal with improvements to e-mail login and ID control. The release makes sure that login links in e-mails keep working and that reminder e-mails always contain the link that the registrant needs. Self-Service Portal Version 6.15.0 will be made available in our production environment on September 24, 2026 at 10:00 CEST. <big>Affected Services</big> • Self-Service Portal Version 6.15.0 <big>Affected Environments</big> • https://selvbetjening.punktum.dk <big>Expected Impact</big> • No downtime is expected during this maintenance window. <big>Changes Included (Self-Service Portal)</big> • E-mail login links now keep working when an e-mail security service checks the link before the user opens it - Before, an automatic check could use up the one-time link, and the user had to request a new one • Reminder e-mails for ID control by e-mail now always include the link to the page where the registrant checks and confirms their data • The "Change name servers" option on the domain page is now only shown to users who are allowed to request a name server change - Registrants and proxies no longer see this option • Minor text corrections <big>Resources</big> • Self-Service Portal Version 6.15.0 Release Notes - https://github.com/Punktum-dk/sb-service-specification/wiki#self-service-portal-version-6150 • Self-Service Portal Service Specification - https://github.com/Punktum-dk/sb-service-specification <big>FAQ</big> • https://punktum.dk/en/faq <big>Support</big> Any questions or concerns regarding these updates can be submitted via our customer support form at https://punktum.dk/en/contact-customer-service

Sandbox Environment UnavailableResolved Aug 31, 2026 · 16h 12mResolved

Dear subscribers Access to our sandbox environment has now been restored. We apologize for the disruption and thank you for your patience. Best regards Punktum dk --- [2026-08-31T10:08:32.858+02:00] (investigating) Dear subscribers Access to our sandbox environment is currently unavailable. This affects both the Registrar Portal and OTE. We are investigating the issue and will provide an update as soon as more information is available. Best regards Punktum dk

Registrar portal transaction history partially unavailableResolved Aug 5, 2026 · 143h 15mResolved

This incident has been resolved. --- [2026-08-05T14:50:49.618+02:00] (investigating) Dear subscribers, The hotfix deployed yesterday only partially resolved the issue affecting transaction history in the registrar portal. Transactions dated after 30 July 2026 are currently not visible. We are continuing our work on a permanent solution and will provide an update when the issue has been fully resolved. We apologise for the inconvenience. Best regards Punktum dk

.dk Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a .dk incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average · 6 days with incidentsSep 25

Live .dk Outage Reports

Problems reported by engineers using .dk. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No .dk problems reported yet.

Something wrong with .dk on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About .dk

.dk publishes a public status page at status.punktum.dk covering 20 components, including DNS (.dk), a.nic.dk and b.nic.dk. PulsAPI tracks .dk outages, degraded performance and incident history in real time, alongside the rest of your SaaS stack.

Over the past 30 days, PulsAPI has measured .dk uptime at 99.88%. Response times, incident history, and SLA tracking for .dk are available on the PulsAPI dashboard.

.dk Status FAQ

Is .dk down right now?

The verdict at the top of this page comes from the latest poll of the official .dk status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if .dk is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until .dk recovers.

How do I check .dk uptime history?

PulsAPI tracks .dk uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.88%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever .dk changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect .dk outages?

PulsAPI reads the official .dk status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual .dk components?

Yes. PulsAPI monitors 19 individual .dk components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when .dk goes down?

Yes. Create a free account and subscribe to .dk: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with .dk to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot .dk problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor .dk?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so .dk plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track .dk with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services