urlscan.io logo urlscan.io
SecurityTrails logo

www.dnscheck.tools Open in urlscan Pro
172.67.188.178  Public Scan

Back to summary
Submitted URL: http://dnscheck.tools/
Effective URL: https://www.dnscheck.tools/
Submission: On April 21 via manual from US — Scanned from US

Form analysis 0 forms found in the DOM

Text Content

DNSCHECK.TOOLS

Results About
Hello! Your public IP addresses are:
Nexeon Technologies
 * 96.9.249.37 ptr: server1.newbehind.com Buffalo, New York, US
 * 2602:ffc8:2:104::15 ptr:
   5-1-0-0-0-0-0-0-0-0-0-0-0-0-0-0-4-0-1-0-2-0-0-0-8-c-f-f-2-0-6-2.reverse-dns
   Buffalo, New York, US

Your DNS resolvers are:
CLOUDFLARE_2400_CB00_0000_36
 * 2400:cb00:16:1024::a29e:4d0a ns: chloe.ns.cloudflare.com Ashburn, Virginia,
   US
 * 2400:cb00:350:1024::ac46:211f ns: chloe.ns.cloudflare.com Ashburn, Virginia,
   US
 * 2400:cb00:350:1024::ac46:2120 ns: chloe.ns.cloudflare.com Ashburn, Virginia,
   US
 * 2400:cb00:352:1024::ac46:290f ns: chloe.ns.cloudflare.com Ashburn, Virginia,
   US
 * 2400:cb00:352:1024::ac46:29be ns: chloe.ns.cloudflare.com Ashburn, Virginia,
   US
 * 2400:cb00:352:1024::ac46:29bf ns: chloe.ns.cloudflare.com Ashburn, Virginia,
   US
 * 2400:cb00:354:1024::ac46:8525 ns: chloe.ns.cloudflare.com Ashburn, Virginia,
   US
 * 2400:cb00:354:1024::ac46:8526 ns: chloe.ns.cloudflare.com Ashburn, Virginia,
   US
 * 2400:cb00:354:1024::ac46:8527 ns: chloe.ns.cloudflare.com Ashburn, Virginia,
   US
 * 2400:cb00:413:1024::ac46:ad26 ns: chloe.ns.cloudflare.com Ashburn, Virginia,
   US
 * 2400:cb00:413:1024::ac46:ad27 ns: chloe.ns.cloudflare.com Ashburn, Virginia,
   US
 * 2400:cb00:413:1024::ac46:ad29 ns: chloe.ns.cloudflare.com Ashburn, Virginia,
   US
 * 2400:cb00:572:1024::ac47:bd16 ns: chloe.ns.cloudflare.com Ashburn, Virginia,
   US
 * 2400:cb00:572:1024::ac47:bd17 ns: chloe.ns.cloudflare.com Ashburn, Virginia,
   US
 * 2400:cb00:573:1024::ac47:c116 ns: chloe.ns.cloudflare.com Ashburn, Virginia,
   US
 * 2400:cb00:573:1024::ac47:c118 ns: chloe.ns.cloudflare.com Ashburn, Virginia,
   US
 * 2400:cb00:601:1024::ac47:dd10 ns: chloe.ns.cloudflare.com Ashburn, Virginia,
   US
 * 2400:cb00:601:1024::ac47:dddd ns: chloe.ns.cloudflare.com Ashburn, Virginia,
   US
 * 2400:cb00:601:1024::ac47:ddde ns: chloe.ns.cloudflare.com Ashburn, Virginia,
   US
 * 2400:cb00:626:1024::ac46:2511 ns: chloe.ns.cloudflare.com Ashburn, Virginia,
   US
 * 2400:cb00:626:1024::ac46:259f ns: chloe.ns.cloudflare.com Ashburn, Virginia,
   US
 * 2400:cb00:626:1024::ac46:25a0 ns: chloe.ns.cloudflare.com Ashburn, Virginia,
   US

Google
 * 74.125.18.3 ns: ns1.google.com Washington, Washington, D.C., US
 * 74.125.18.69 ns: ns1.google.com Washington, Washington, D.C., US
 * 172.253.8.132 ns: ns1.google.com Washington, Washington, D.C., US
 * 172.253.8.134 ns: ns1.google.com Washington, Washington, D.C., US
 * 172.253.8.138 ns: ns1.google.com Washington, Washington, D.C., US
 * 172.253.8.139 ns: ns1.google.com Washington, Washington, D.C., US
 * 172.253.10.1 ns: ns1.google.com Washington, Washington, D.C., US
 * 172.253.10.2 ns: ns1.google.com Washington, Washington, D.C., US
 * 172.253.195.193 ns: ns1.google.com Washington, Washington, D.C., US
 * 172.253.195.198 ns: ns1.google.com Washington, Washington, D.C., US
 * 172.253.195.200 ns: ns1.google.com Washington, Washington, D.C., US
 * 172.253.195.201 ns: ns1.google.com Washington, Washington, D.C., US
 * 172.253.210.6 ns: ns1.google.com Reston, Virginia, US
 * 172.253.210.68 ns: ns1.google.com Reston, Virginia, US
 * 172.253.210.71 ns: ns1.google.com Reston, Virginia, US
 * 172.253.213.3 ns: ns1.google.com Washington, Washington, D.C., US
 * 172.253.213.4 ns: ns1.google.com Washington, Washington, D.C., US
 * 172.253.213.5 ns: ns1.google.com Washington, Washington, D.C., US
 * 172.253.213.6 ns: ns1.google.com Washington, Washington, D.C., US
 * 172.253.214.7 ns: ns1.google.com Washington, Washington, D.C., US
 * 172.253.214.99 ns: ns1.google.com Washington, Washington, D.C., US
 * 172.253.214.100 ns: ns1.google.com Washington, Washington, D.C., US
 * 172.253.221.131 ns: ns1.google.com Washington, Washington, D.C., US
 * 172.253.221.138 ns: ns1.google.com Washington, Washington, D.C., US
 * 172.253.223.199 ns: ns1.google.com Washington, Washington, D.C., US
 * 172.253.223.201 ns: ns1.google.com Washington, Washington, D.C., US
 * 172.253.223.202 ns: ns1.google.com Washington, Washington, D.C., US
 * 192.178.65.1 ns: ns1.google.com Washington, Washington, D.C., US
 * 192.178.65.6 ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c00::104 ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c02::104 ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c03::103 ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c04::101 ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c05::103 ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c05::105 ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c06::101 ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c08::102 ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c09::103 ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c09::104 ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c09::106 ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c09::108 ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c09::10a ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c0b::101 ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c0b::102 ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c0b::103 ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c0b::104 ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c0b::109 ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c17::101 ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c17::104 ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c17::106 ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c17::107 ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c17::10a ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c17::10e ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c19::101 ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c19::103 ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c19::107 ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c19::108 ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c1b::105 ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c1b::108 ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c1d::101 ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c1d::103 ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c1d::106 ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c1d::10a ns: ns1.google.com Washington, Washington, D.C., US
 * 2607:f8b0:4004:c1f::109 ns: ns1.google.com Washington, Washington, D.C., US

Your DNS security:

ECDSA P-256ECDSA P-384Ed25519Good signature✓……Bad signature✓……Expired
signature✓……Missing signature………

See more tools at addr.tools


ABOUT

dnscheck.tools is a tool to test for DNS leaks, DNSSEC validation, and more.


USAGE

Load dnscheck.tools in any web browser to identify your current DNS resolvers
and check DNSSEC validation.


DNS TEST QUERIES

dnscheck.tools is also a custom DNS test server! Make test queries like:

$ dig [SUBDOMAIN.]go[-ALG][-NET].dnscheck.tools TXT


SUBDOMAIN

The SUBDOMAIN is composed of DNS response options, separated by a hyphen.
Options may include:

 * any of:
   * <random> - a random number, up to 8 hexadecimal digits; useful for cache
     busting
   * compress - force the use of DNS message compression in the response
   * [no]truncate - force or disable message truncation for responses over UDP
   * watch - mirror corresponding requests to the /watch/<random> page; requires
     <random>
 * up to one of:
   * padding<n> - add <n> bytes of EDNS0 padding, up to 4000, to A, AAAA, and
     TXT responses
   * txtfill<n> - add <n> bytes of padding as TXT data, up to 4000, to TXT
     responses
 * up to one of:
   * formerr - respond with "format error"
   * servfail - respond with "server failure"
   * notimpl - respond with "not implemented"
   * refused - respond with "query refused"
   * noreply - do not respond
 * up to one of:
   * nosig - do not provide any DNSSEC signature in the response
   * badsig - provide an invalid DNSSEC signature when signing the response
   * expiredsig[<t>] - provide an expired DNSSEC signature when signing the
     response, <t> seconds in the past (default 1 day)


ALG & NET

The zone, go[-ALG][-NET], sets DNSSEC signing and network options.

 * ALG may be one of:
   * alg13 - sign the zone using ECDSA P-256 with SHA-256 (default)
   * alg14 - sign the zone using ECDSA P-384 with SHA-384
   * alg15 - sign the zone using Ed25519
   * unsigned - do not sign the zone
 * NET may be one of:
   * ipv4 - offer only IPv4 authoritative nameservers
   * ipv6 - offer only IPv6 authoritative nameservers

The zone "go" is equivalent to "go-alg13" and has both IPv4 and IPv6
authoritative nameservers.


EXAMPLES

See some information about your DNS resolvers:

$ dig go.dnscheck.tools TXT

For our Windows friends:

> nslookup -q=TXT go.dnscheck.tools

Getting cached results? Introduce a random number:

$ dig 123456.go.dnscheck.tools TXT

Test if your resolvers are validating DNSSEC. This should produce an error:

$ dig badsig-123456.go.dnscheck.tools TXT

Want to watch a stream of DNS requests coming from your resolvers? Goto
dnscheck.tools/watch/123456 and specify the watch option:

$ dig watch-123456.go.dnscheck.tools TXT


SEE ALSO

addr.tools


CONTACT

On reddit, u/dnschecktool


THIRD-PARTY DATA

IP addresses are grouped by their network registrants as discovered by the
Registration Data Access Protocol.

Hostnames (pointer records) and authoritative nameservers are discovered by
reverse DNS resolution.

IP geolocation data is provided by ipinfo.io.


PRIVACY POLICY

No personal data is collected. This site doesn't use cookies. Cheers!

EDNS ECS IPv6
dns requests: 141