Match the symptom, then work through the safe checks.
1. What best matches what you observe?
2. Complete only the checks that are safe for you.
Show stop conditions
- The domain is used for banking, identity, or payment and redirects unexpectedly
- A managed device requires network administrator changes
Likely causes
- The web address is misspelled or no longer exists
- The current DNS resolver cannot answer correctly
- A VPN, private DNS, parental filter, or security product is intercepting DNS
- The router or device has stale DNS state
Quick checks, in order
Check the address carefully
Remove extra characters and test the site home page.
Try the domain on mobile data
If it works there, the local network or DNS resolver is the likely difference.
Restart the browser and router
This clears common temporary resolver and gateway states.
Review custom DNS or filtering settings
Return to automatic DNS temporarily if you intentionally use a custom resolver.
Does the domain resolve elsewhere?
The domain may be invalid, expired, or having authoritative DNS trouble.
Focus on home router DNS, provider DNS, filters, or local configuration.
Focus on that device’s DNS cache, VPN, private DNS, or security software.
Stop and get qualified help when
- The domain is used for banking, identity, or payment and redirects unexpectedly
- A managed device requires network administrator changes
Official support and model manuals
Use the full model number from the rating label. The manufacturer manual is the deciding reference when codes differ by region or product family.
Frequently asked questions
What does NXDOMAIN mean?
It means the resolver reports that the requested domain name does not exist in DNS.
Can changing DNS fix it?
Sometimes, but only when the current resolver or filter is the cause. It cannot fix a genuinely missing domain.