Verisign Public DNS outages and problems
No user reports came in for Verisign Public DNS in the past 24 hours, and its uptime over that window is 100.00%.
No 15-minute window had any reports at all, so the chart above stays flat.
What people can report about Verisign Public DNS
People who report a problem with Verisign Public DNS to the outage-report feed behind this page can tag what is affected. These are the categories they can pick; the feed shows no counts per category:
- Website
- Hosting
- Login
- Server connection
- File access
- Domains
- DNS
- API
- Dashboard
- Storage and backup
- Databases
Verisign Public DNS reports around the world
In the last 24 hours, 3 problem reports about Verisign Public DNS came in from 2 countries. Right now reports are at the usual level in every country.
- Outage now
- Problems now
- Normal
| Country | Now | Last hour | 24 hours |
|---|---|---|---|
| Algeria | Normal | 0 | 2 |
| Brazil | Normal | 0 | 1 |
| The US | Normal | 0 | 0 |
| The UK | Normal | 0 | 0 |
| Mexico | Normal | 0 | 0 |
| The Netherlands | Normal | 0 | 0 |
| Germany | Normal | 0 | 0 |
| Belgium | Normal | 0 | 0 |
| France | Normal | 0 | 0 |
| Russia | Normal | 0 | 0 |
| Italy | Normal | 0 | 0 |
| India | Normal | 0 | 0 |
Each country's status compares its reports with the usual level there. 60 more countries had 0 reports in the last 24 hours. Map outlines: Natural Earth.
Verisign Public DNS problem spikes, last 30 days
Since 5 October, Verisign Public DNS had no outage spikes or periods of elevated reports.
- Sat 3 Oct: no data
- Sun 4 Oct: no data
- Mon 5 Oct: 0 reports
- Tue 6 Oct: 0 reports
- Wed 7 Oct: 0 reports
- Thu 8 Oct: 0 reports
- Fri 9 Oct: 0 reports
- Sat 10 Oct: 0 reports
- Sun 11 Oct: 0 reports
- Mon 12 Oct: 0 reports
- Tue 13 Oct: 0 reports
- Wed 14 Oct: 0 reports
- Thu 15 Oct: 0 reports
- Fri 16 Oct: 0 reports
- Sat 17 Oct: 0 reports
- Sun 18 Oct: 0 reports
- Mon 19 Oct: 0 reports
- Tue 20 Oct: 0 reports
- Wed 21 Oct: no data
- Thu 22 Oct: 0 reports
- Fri 23 Oct: 0 reports
- Sat 24 Oct: 0 reports
- Sun 25 Oct: 0 reports
- Mon 26 Oct: 0 reports
- Tue 27 Oct: 0 reports
- Wed 28 Oct: 0 reports
- Thu 29 Oct: 0 reports
- Fri 30 Oct: 0 reports
- Sat 31 Oct: 0 reports
- Sun 1 Nov: no data
By country
Each square is one day in the countries with the most reports: red when reports stayed at outage level for half an hour or more, amber when they stayed above the usual level for an hour or more, grey otherwise.
- Algeria2
- Poland2
- Brazil1
- Colombia1
- Nigeria1
- Pakistan1
- The US1
- The UAE0
Country history starts on 28 October 2026. Days run from midnight to midnight, Central European time.
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 5 October 2026. Monthly reports for all services
How to fix Verisign Public DNS not working
Verisign Public DNS is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:
Your browser tries to reach verisign.com over your own connection, right now. Nothing is sent to us or stored.
Remove Verisign Public DNS from your device
Open your network adapter's DNS settings and clear the addresses for this service; on Windows, go to Settings > Network & Internet > Wi-Fi or Ethernet > Hardware properties > DNS server assignment and set it to Automatic (DHCP), and on macOS, open System Settings > Network > Wi-Fi or Ethernet > Details > DNS and delete the custom entries. Save, then reconnect to the network.
Flush DNS for Verisign Public DNS
If one device still fails to resolve sites, clear the local cache: on Windows, open Command Prompt as administrator and run ipconfig /flushdns, and on macOS, run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder in Terminal. Then load a site you have not visited recently.
Query the resolver directly
Open Command Prompt or Terminal and run nslookup, then type server followed by the resolver address you configured and type a domain you know. If the query times out, your device cannot reach the service, so try a different network or turn off any VPN.
Override Verisign Public DNS on the router
Log in to your router's admin page and open the DHCP or Internet settings. Replace the DNS servers there with a different provider, then reboot the router and reconnect your device. This catches devices that ignore the DNS you set on the computer.
While Verisign Public DNS is down: what to use instead
- Google Public DNS Switch your device or router to it when you want a large public resolver and your DNS resolver has stopped answering.
- Cloudflare DNS Try this one if you prefer a public resolver that you can set on a single computer first, then on the router after it works.
- OpenDNS Use it on a home network when you want optional filtering for the devices connected to that network.
- Quad9 Pick it if you want a resolver that blocks known malicious domains, which can help when a site resolves to the wrong place.
Fix Verisign Public DNS on Windows, Mac, Android and iPhone
Verisign Public DNS on Windows
- Fix
- If Verisign Public DNS is failing on Windows, open your Network Connections, access your adapter properties, and temporarily revert your IPv4 DNS settings to automatic. You can also flush your DNS resolver cache through system settings to clear corrupted routing.
- Check
- To see if Verisign Public DNS is down on Windows, use network diagnostic tools to query a website using Verisign's specific server address. If the query times out but direct IP connections work, the DNS service is offline.
ping verisign.comTest whether Verisign Public DNS's servers replynslookup verisign.comCheck that Verisign Public DNS's DNS resolvestracert verisign.comTrace where the connection dropsipconfig /flushdnsClear the DNS cache, then reloadVerisign Public DNS on Mac
- Fix
- To fix Verisign Public DNS issues on macOS, go to System Settings, select Network, and modify your active connection's DNS settings to use automatic DHCP or an alternative provider. Applying these changes will route your traffic away from the unresponsive Verisign servers.
- Check
- Check if Verisign Public DNS is down on a Mac by testing domain resolution using diagnostic utility tools pointed at Verisign's IP address. If the lookup fails while your physical internet connection is active, the service is experiencing an outage.
ping -c 4 verisign.comTest whether Verisign Public DNS's servers replynslookup verisign.comCheck that Verisign Public DNS's DNS resolvestraceroute verisign.comTrace where the connection dropssudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderFlush the macOS DNS cache, then reloadVerisign Public DNS on Android
- Fix
- To resolve Verisign Public DNS issues on Android, open your Wi-Fi settings, select your network, and change the IP settings from static back to DHCP. Alternatively, disable any custom Private DNS settings to stop routing traffic through Verisign.
- Check
- Determine if Verisign Public DNS is down on Android by checking if web pages load only when you disable your custom DNS settings. If internet access restores immediately after removing Verisign's IPs, the DNS servers are down.
Verisign Public DNS on iPhone and iPad
- Fix
- Fix Verisign Public DNS on an iPhone or iPad by navigating to iOS Wi-Fi settings, tapping the information icon on your network, and changing Configure DNS to Automatic. This removes the Verisign IPs and restores your default carrier or router DNS.
- Check
- To verify if Verisign Public DNS is down on iOS, try loading a standard webpage while connected to a Wi-Fi network configured with Verisign's DNS. If the connection fails but works when switching to cellular data, Verisign is likely down.
What happens when Verisign Public DNS goes down
Verisign Public DNS is a public recursive resolver. If your router or phone uses it instead of your ISP's resolver, an outage interrupts name lookups for every site you have not already cached, so browsers and apps stall when they need a fresh address.
Name lookups fail first: pages you have not already cached stop opening, while sites you visited recently may still load for a short time. Browser warnings that a site's address cannot be found appear, and apps that call new domains hang or time out. Email servers and game clients that need fresh lookups can drop connections. Trouble often hits one region or network path while another keeps answering.
Verisign Public DNS IP address, servers and network
- IPv4 addresses
- 3.173.21.153
Show all 3
- 3.173.22.153
- 3.173.23.153
- IPv6 addresses
- 2600:9000:2715::9700:c8:4:9d02
Show all 3
- 2600:9000:2716::9700:c8:4:9d02
- 2600:9000:2717::9700:c8:4:9d02
- Network
- AS16509 · Amazon.com, Inc., registered in the United States
- Served through
- Amazon CloudFront · our check was answered by its Frankfurt (FRA) data centre
- DNS hosted by
- its own name servers (nstld.com)
- HTTPS certificate
- Issued by DigiCert Inc, valid until 26 Nov 2026 (25 days)
- HTTP/3
- Not advertised
- Our check
- Answered in 325 ms
Checked from our server in Frankfurt, Germany, 2 days ago, for www.verisign.com. A service behind a CDN answers from many data centres, usually the one nearest to you, so these addresses are where its traffic enters, not where its own servers stand. Visitors elsewhere may see different addresses.
Checked from 11 places around the world
All 11 locations got an answer from www.verisign.com. Fastest from Milan (12 ms), slowest from Tokyo (546 ms). Every location connected through Amazon.com, Inc. (AS16509), using 3 different addresses.
| Location | Result | Time | Address reached |
|---|---|---|---|
| FrankfurtGermany | Up | 25 ms | 3.173.21.153 |
| ViennaAustria | Up | 19 ms | 3.173.21.153 |
| MilanItaly | Up | 12 ms | 3.173.23.153 |
| ParisFrance | Up | 53 ms | 3.173.21.153 |
| AmsterdamNetherlands | Up | 37 ms | 3.173.22.153 |
| MadridSpain | Up | 26 ms | 3.173.23.153 |
| WarsawPoland | Up | 93 ms | 3.173.21.153 |
| Los AngelesUSA | Up | 43 ms | 3.173.22.153 |
| São PauloBrazil | Up | 40 ms | 3.173.22.153 |
| SingaporeSingapore | Up | 33 ms | 3.173.22.153 |
| TokyoJapan | Up | 546 ms | 3.173.23.153 |
Checked with check-host.net from its servers in these cities 2 days ago, for www.verisign.com. Time is how long each server took to load the page.
Verisign Public DNS FAQ
Is Verisign Public DNS down right now?
Did Verisign Public DNS support DNSSEC?
Why does my router still send queries to Verisign Public DNS?
Does Verisign Public DNS block malware or adult sites?
Can I use Verisign Public DNS on a PlayStation or Xbox?
How we track Verisign Public DNS
The status on this page comes from user-submitted problem reports for Verisign Public DNS, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for Verisign Public DNS, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. Verisign Public DNS doesn't publish a public status page that we know of, so user reports are often the quickest sign that something is wrong on their side.