A few FQDN could be used to test and validate that your device is currently protected by the secureDNS service:
You could do a DNS resolution on the following hosts:
botnet.tests.secure-dns.eu
malware.tests.secure-dns.eu
phishing.tests.secure-dns.eu
apt.tests.secure-dns.eu
spam.tests.secure-dns.eu
newdom.tests.secure-dns.eu
Those should be resolved as the following:
botnet.tests.secure-dns.eu. -> botnet.sinkhole.secure-dns.eu.
botnet.sinkhole.secure-dns.eu. -> 152.228.249.240
malware.tests.secure-dns.eu. -> malware.sinkhole.secure-dns.eu.
malware.sinkhole.secure-dns.eu. -> 152.228.249.241
phishing.tests.secure-dns.eu. -> phishing.sinkhole.secure-dns.eu.
phishing.sinkhole.secure-dns.eu. -> 152.228.249.242
apt.tests.secure-dns.eu. -> apt.sinkhole.secure-dns.eu.
apt.sinkhole.secure-dns.eu. -> 152.228.249.240
spam.tests.secure-dns.eu. -> spam.sinkhole.secure-dns.eu.
spam.sinkhole.secure-dns.eu. -> 152.228.249.243
newdom.tests.secure-dns.eu. -> new.sinkhole.secure-dns.eu.
new.sinkhole.secure-dns.eu. -> 152.228.249.245
Please note that you might have a different IP if you have configured an overwrite in your DNS server for the zone sinkhole.secure-dns.eu