Know what you are looking at.
myip.dk has been online since 2000.
myip.dk brings together the small checks that make network troubleshooting easier: your public addresses, DNS answers, registry records, and subnet calculations. Each tool explains both its results and its limits.
Requests reach the site through a content delivery network, which forwards your address to our server. For you, that means the address shown is the one our network edge observes when this browser connects.
Checks with a clear scope
Connection tests make HTTPS requests from your browser to our IPv4, IPv6, and dual-stack hostnames. Network and DNS lookups query fixed data providers. We do not initiate port scans or connection probes against the addresses visitors enter.
Our DNS comparison reflects resolver responses from our server’s location. Network lookups show registry records, reverse DNS, and optional routing data; they do not identify individuals, determine an exact physical location, or establish whether an address is safe.
Who runs myip.dk
myip.dk is run by Michael N. Jensen. Questions, corrections, and privacy requests are welcome at [email protected].
Privacy & data use
The data controller for this site is Michael N. Jensen. Contact: [email protected].
Loading the site and running connection checks exposes your IP address and normal request information to our content delivery network and origin infrastructure. The infrastructure can process request logs for service operation and security. This site does not promise anonymous or log-free access.
| Feature | Data sent | Where it goes |
|---|---|---|
| Public IP / connection check | Your browser’s connection metadata | Our content delivery network and the myip.dk origin |
| IP lookup | The IP address you enter | Our server, the regional registry selected through IANA, and Cloudflare DNS for PTR. |
| DNS lookup | The DNS name or PTR address and record type | Our server and your selected resolver: Cloudflare or Google |
| Email DNS check | The domain and optional DKIM selector | Our server and Cloudflare DNS |
| Browser information | One request whose headers are echoed back; device details are not transmitted | Our server; everything else stays in your browser |
| IP converter | No input is transmitted | Calculated in your browser |
| Subnet calculator | No calculator input is transmitted | Calculated in your browser |
| Connection history / router WAN comparison | Normal connection checks; entered WAN values are not transmitted | History, baselines, and entered WAN values stay in browser memory until you leave or reload |
The application does not include advertising, analytics, third-party font requests, or application cookies. A language chosen in the menu is remembered in this browser’s local storage. Our content delivery network may apply its own service and security behavior. External providers handle requests under their own policies; avoid putting confidential names into a public DNS lookup.
For additional information, see Cloudflare’s privacy policy, Google Public DNS privacy information, and RIPE NCC’s privacy statement.
Data sources, not guarantees
When a network operator name is shown next to your address, it comes from the IP to ASN Lite database by DB-IP. The lookup happens on our server; your address is not sent to DB-IP.
Registration records, routing announcements, and DNS records can change. Registry country is an administrative field, not the visitor’s location. The lookup selects ARIN, RIPE NCC, APNIC, LACNIC, or AFRINIC through IANA’s IPv4/IPv6 mappings. Some national-registry referrals are not supported and are shown as unavailable. A reverse DNS name may be outdated, and a lookup provider may be temporarily unavailable. Treat the output as one piece of evidence when diagnosing a connection.
The guides use documented examples and link to source material. They are designed to help you understand the result before changing your network configuration.