DNS poisoning test
Also known as a DNS hijacking test. Enter a domain to see whether its DNS answers look abnormal or poisoned.
Enter a domain to start
Our detection engine compares the domain's DNS answers from several regions in real time. The result page shows the target, the result and the check time.
Checking for DNS poisoning…
Result
Enter a domain to start
Results will appear here
About DNS poisoning tests
The DNS poisoning test, also called a DNS hijacking test, uses a detection system built by TCPING.CN to cross-check DNS answers from multiple nodes and spot abnormal, poisoned or hijacked resolution. Enter a domain to see the result, check time and target. It is a quick first step when a site will not open, loads unusually slowly or has just changed DNS.
Treat the result as a pre-check and troubleshooting aid, not a replacement for a manual check on real devices. Network conditions, the resolution path and the target's status can all affect live results, so when something looks wrong, compare it with the DNS lookup, real access results and a manual retest.
Frequently asked questions
How does the DNS poisoning test decide the result?
TCPING.CN sends DNS queries for the domain from several nodes and cross-checks the answers. If an answer is abnormal, unexpected or points to an illegitimate address, the domain is flagged as possibly poisoned. The result, target and check time are then shown.
What are DNS poisoning and DNS hijacking?
DNS poisoning means a resolver returns a wrong or tampered IP address, so a working site fails to open, redirects unexpectedly or loads slowly. DNS hijacking usually means an intermediary intercepts the query and forces a specific answer. The symptoms are similar, so this tool treats both as poisoning.
What does "No poisoning found" mean?
It means this check found no clear sign of poisoning. It is useful for quick confirmation during troubleshooting or after changes, but the status can change later. You can also use the DNS lookup tool to compare resolution results across regions.
Why does it sometimes say "Unable to confirm"?
This usually means the check could not collect enough consistent evidence, often because of network fluctuations or an unusual response from the target. Try again later and compare with DNS lookups and real access results.
When is this check useful?
Typical uses include quick troubleshooting when a site will not open, verification after a domain change, path checks before a campaign page goes live, and pre-checks after users report access problems. Keep a manual check on real devices for business decisions.