Test Your DNSWatch Protection
When you have DNSWatch protection, you should be able to browse to non-malicious sites without a problem. If you attempt to access a filtered content or malicious site, you should see a block page instead of the requested domain.
There are two tests to confirm the DNSWatch functions correctly:
- Verify you can browse to non-malicious or regular domains, such as https://www.watchguard.com without issues
- Verify DNSWatch blocks malicious or filtered content domains, such as test.strongarm.io .
Verify DNSWatch Blocks Malicious or Filtered Content Domains
You can perform this test on a DNSWatch protected network or on a portable device with DNSWatchGO Client installed.
If you run the test on a portable device to test DNSWatchGO Client, make sure the device is not connected to a DNSWatch protected network when you perform the test for accurate results.
- In your browser, go to test.strongarm.io.
- Confirm the correct block page appears.
If DNSWatch correctly blocks the test domain, you see this block page:
If DNSWatch does not operate correctly, you see this message:
Test DNSWatchGo Client
DNSWatch is currently in beta with Content Filter Policies for Firebox. Some features are only available in the DNSWatch beta. For DNSWatch beta documentation, log in to the WatchGuard Beta test community.
DNSWatchGO Client protects your devices when they are off your protected network. After you test the application in several scenarios, report the results on the WatchGuard beta management platform.
To gather the best data for the test, you should repeat the test scenarios on DNSWatchGO Client devices in a variety of locations. Some suggested locations:
- Home
- Active Directory controlled network
- Coffee shops
- Mobile hotspot
- On a network behind a firewall while connected with VPN
- Airport — Include the airport and the name of the service used
- Airplane — Include the airline and name of the service used
- Hotels — Include the hotel chain name
It is important to test the client on networks that are not protected by DNSWatch on your Firebox or other DNSWatch enabled network.