DNS Visualisation (DomainMON)
DomainMON allows you to use your own RIPE Atlas credits to monitor name servers of your DNS domains. It provides a means to monitor the quality of service offered by your name servers, and is powered by the same technology as DNSMON, which monitors various important DNS root and Top-Level Domain name servers.
The tool is at atlas.ripe.net/use-cases/domain-monitoring (Domain Monitoring in the Use Cases menu). You need to be logged in to create and manage DomainMONs. Anyone with a share link can view a visualisation (see Sharing a visualisation).
Getting started
To start monitoring a domain, log in, open the DomainMON page and click Monitor a Domain (or Add a domain to monitor if you already have some). If you are not logged in, the button reads Login to use DomainMON and takes you to the login page first.

A wizard opens with three steps:
Enter domain
The name of your main DNS domain. This should usually be a DNS zone with a SOA record, rather than a subdomain. Click Continue to look up its name servers.
Select servers
The servers that you wish to monitor to see whether they are serving your domain.
- Suggested servers are taken from the NS records for your domain. Each address is listed as its own row, because A and AAAA records are used to set up separate measurement targets for IPv4 and IPv6 where available.
- Tick Include this server? for each address you want to measure, or use the header checkbox to select them all.
- If the domain already has a DomainMON, its Existing servers are listed above the suggestions.
- If the domain is already monitored by DNSMON, a banner says so and links to it there.
Configure probes and measurements
In this step, you can define exactly how you want to monitor your domain. The total daily credit cost of your measurements will be determined by the options that you choose, and is displayed dynamically in the Costs summary box. The box shows your current balance, the daily cost, your daily income and, where relevant, how many days your credits will last.
Probes
You can define groups of probes to carry out your measurements. Each group is a number of probes (10 by default) from one of these sources:
- area: a world area, such as WW (Worldwide)
- country
- asn
- msm: the same probes as an existing measurement ID
- prefix: an IP prefix
- probes: a comma-separated list of probe IDs
Use Add more probes to add another group. You may not include more than 50 probes. The number of probes that you choose here will affect the overall cost of your measurements. If the domain already has monitored servers, you can tick Use the same probes as previous measurements instead.
Measurements
You can choose the types of measurements that will be carried out, and how often they will be executed:
| Type | Default interval |
|---|---|
| UDP SOA | 3600 seconds |
| TCP SOA | 3600 seconds |
| ICMP Traceroute | 3600 seconds |
Intervals can be set between 60 and 86400 seconds. At least one DNS measurement (UDP SOA or TCP SOA) must be enabled, and ICMP Traceroute is only available alongside one. If the domain already has monitored servers, Copy existing measurements for this domain reuses their settings. The more measurements that you run, or the more often that you run them, the more credits that you will spend per day.
Click Monitor to create the measurements. You are then taken to the new domain's page.
Managing your domains
The DomainMON page lists your monitored domains with their number of Targets, Measurements and Daily cost, plus a Total row. Click a domain to open its page, which has two tabs: Overview and Visualisation.
Overview tab
The Overview tab shows the domain's Daily cost, Total measurements and Group ID. The group ID links to the domain's measurements in the measurement list. Below that, Servers and measurements lists each monitored server with its daily cost. From here you can:

- Show measurements / Hide measurements: list a server's measurements with their ID, target, type and daily cost
- Stop: stop the measurements for one server
- Manually Add Servers: reopen the wizard at the Select servers step to add more targets. The new servers use the same probes and measurement types as your existing ones.
- Add all detected servers / Add this server: shown under Detected NS records that are not currently measured when the domain's NS records list servers you aren't measuring. A confirmation shows the estimated daily cost first.
- Stop Monitoring: remove the domain and stop all of its measurements
WARNING
Stopping a server or the whole domain cannot be undone. After Stop Monitoring you no longer have access to the visualisation, but the individual measurements stay available in the measurements section under the same group ID.
Visualising your domain
After your DomainMON measurements have been running for a while, you will be able to visualise them in a grid on the Visualisation tab. The format of this visualisation is the same as DNSMON, and you can find more information in the DNSMON user interface documentation.
At the top level each row is one of your servers. Click a server to drill down to a row per probe. Click the home button to go back to server level. The toolbar has:
| Control | What it does |
|---|---|
| Date/time range | Choose the start and end of the period shown, in UTC. |
| Protocol | Switch between udp and tcp, when the domain is measured over both. |
| Perspective | Choose what the cell colours show: Unanswered queries (%), Response time (ms) or Relative response time (%). |
| Zoom in / out | Narrow or widen the time range. |
| Zoom level menu | Jump to Last 5 hours, Last 1 day, Last 1 week or Last 1 month. |
| Set Color Range | Drag the slider to set which values are coloured green and which red for the current perspective. |
| Show all rows | Reset any row zoom so every row is visible. |
| Fullscreen | Expand the visualisation to fill the screen. |
| Share (🔗) | Copy a link or embed code (see below). |
The Time Range slider below the grid also moves or narrows the period. The status bar shows when the data was last updated and has an Auto-refresh toggle. When auto-refresh is on, the refresh interval follows the resolution of the data shown. It is every 5 minutes for full-resolution data, every 5 minutes to 1 hour for aggregated data, and every 12 hours for daily aggregates.
Click a cell to open Result details. For a probe at full resolution, this shows the data for that cell, with DNS response and Traceroute tabs where available, plus links to the measurements. Otherwise it lists links to the underlying data and measurements.
Sharing a visualisation
When you open the Visualisation tab, the address changes to a public link of the form:

https://atlas.ripe.net/use-cases/domain-monitoring/<domain>/<share code>/visualisationThe share code is generated by RIPE Atlas and encodes the measurement group and the protocols available. Anyone with the link can view the visualisation without logging in, but they can't see or change the Overview tab. A link with only the domain name, such as /use-cases/domain-monitoring/<domain>/, opens only for the domain's owner.
To copy the link, open the Share (🔗) menu in the visualisation toolbar and choose Copy link. The share code doesn't include the time range, so the link opens with the default view.
Embedding the visualisation in your page
The DomainMON visualisation can be embedded in your own pages with an iframe. Open the Share (🔗) menu in the visualisation toolbar and choose Copy embed code. This copies a ready-to-paste snippet:
html
<iframe
src="https://atlas.ripe.net/use-cases/domain-monitoring/<domain>/<share code>/embed"
width="100%"
height="600"
style="border:0"
></iframe>Adjust width and height to suit your layout. The embedded view carries a RIPE Atlas watermark, has no fullscreen control and, when the domain is monitored over multiple protocols, includes a protocol selector. Embed pages are not indexed by search engines.
You can add these query parameters to the src URL:
| Parameter | Meaning |
|---|---|
autoRefresh=true | Start with auto-refresh switched on. It is off by default. |
protocol=udp or protocol=tcp | The protocol to show first. Without it, a TCP-only domain shows TCP, and anything else shows UDP. |
For example: …/<share code>/embed?autoRefresh=true&protocol=tcp.