Skip to content

DNS Checker

See whether a DNS change has reached the rest of the internet. We ask servers in South Africa, across Africa and around the world, and compare each answer with your own nameservers.

IPv4 address of the domain

Compare with a value you expect

Each server is then marked by whether its answer includes this value, instead of by your nameservers.

Where we check from

24 DNS servers, starting with Johannesburg and Cape Town.

Map of the DNS servers we check from
  • Matches
  • Different answer
  • No record
  • No reply

Results by location

South Africa

  • Johannesburg, South Africa Afrihost Ready
  • Cape Town, South Africa Vodacom Ready

Rest of Africa

  • Lagos, Nigeria Spectranet Ready
  • City Stars Global Ready
  • Nairobi, Kenya Safaricom Ready
  • Casablanca, Morocco ASMedi Ready
  • GST Africa Global Ready
  • BBDP1 Global Ready
  • Realtime Global Ready

Rest of the world

  • London, United Kingdom Level 3 Ready
  • Nuremberg, Germany Hetzner Ready
  • Prague, Czechia CZ.NIC Ready
  • Dallas, United States Cisco OpenDNS Ready
  • Ottawa, Canada CIRA Ready
  • Mumbai, India Vodafone Idea Ready
  • Hangzhou, China AliDNS Ready
  • Taipei, Taiwan HiNet Ready
  • Seoul, South Korea KT Ready
  • Melbourne, Australia Telstra Ready

Global networksAnswered from their site nearest our server

  • Google Public DNS Global Ready
  • Cloudflare Global Ready
  • Quad9 Global Ready
  • OpenDNS Global Ready
  • AdGuard DNS Global Ready

Reading the results

Why do some servers still show the old value?

Every DNS server keeps a copy of an answer for as long as the record's TTL (time to live) allows, then asks again. Until that time runs out, it keeps giving the old answer. Most changes reach everyone within a few hours. A change of nameservers can take up to 48 hours.

What does "your nameservers say" mean?

We ask the nameservers in charge of your domain directly, so their answer is always the newest one. A server that matches them has the change. If your nameservers show the old value, the change was not saved, or it was made at a different DNS provider.

Some servers give a different answer, but nothing changed

Large services such as Microsoft 365 and content networks give different addresses in different places on purpose. For those, different answers are normal. Use Expected value to check for the one that matters.

A server shows "No reply"

That server did not answer in time. It is a problem with that server, not with your domain, as long as the others answer.

Checking email records

Choose SPF, DMARC, DKIM, MTA-STS, TLS-RPT or BIMI under Email in the record list. We look in the right place for each, so you only type your domain.

Back to Trinico Cloud

Loading