[{"data":1,"prerenderedAt":10},["ShallowReactive",2],{"article:pt-br:public-dns-server-addresses":3},{"locale":4,"slug":5,"path":6,"title":7,"description":8,"html":9},"pt-br","public-dns-server-addresses","\u002Fpt-br\u002Flearn\u002Fpublic-dns-server-addresses\u002F","DNS públicos de longa duração: endereços e opções por região","Endereços IPv4, IPv6 e DNS criptografado de serviços antigos, com modos claros e critérios regionais sem prometer o mais rápido para todos.","\u003Ch2>Como ler a lista\u003C\u002Fh2>\n\u003Cp>Há registros públicos desses serviços operando há pelo menos cinco anos. Endereços conferidos na documentação oficial em 2026-10-21. A trajetória não garante continuidade futura nem acesso pela sua rede. Cada provedor aparece em um único modo, sem misturar filtros familiares ou outros perfis.\u003C\u002Fp>\n\u003Ch2>Escolher para sua rede\u003C\u002Fh2>\n\u003Cp>Google, Cloudflare, Quad9 e AdGuard são candidatos internacionais. Nas redes chinesas, AliDNS e DNSPod podem entrar na comparação; na Rússia e arredores, Yandex. Não é um ranking de velocidade. Considere acessibilidade, estabilidade, filtros e privacidade. Nomes internos de empresas e escolas podem exigir o resolvedor indicado por elas. DoH e DoT criptografam consultas até o resolvedor; não são VPN e não tornam toda atividade anônima.\u003C\u002Fp>\n\u003Ch2>Google Public DNS\u003C\u002Fh2>\n\u003Cp>Resolução geral para usuários globais; não voltada principalmente a bloquear anúncios ou conteúdo familiar.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>IPv4: \u003Ccode>8.8.8.8\u003C\u002Fcode>, \u003Ccode>8.8.4.4\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>IPv6: \u003Ccode>2001:4860:4860::8888\u003C\u002Fcode>, \u003Ccode>2001:4860:4860::8844\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>DoH: \u003Ccode>https:\u002F\u002Fdns.google\u002Fdns-query\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>DoT: \u003Ccode>dns.google\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Documentação oficial: \u003Ca href=\"https:\u002F\u002Fdevelopers.google.com\u002Fspeed\u002Fpublic-dns\u002Fdocs\u002Fusing\" rel=\"nofollow noopener noreferrer\">Google Public DNS 1\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fdevelopers.google.com\u002Fspeed\u002Fpublic-dns\u002Fdocs\u002Fsecure-transports\" rel=\"nofollow noopener noreferrer\">Google Public DNS 2\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Registro público: \u003Ca href=\"https:\u002F\u002Fgoogleblog.blogspot.com\u002F2009\u002F12\u002Fintroducing-google-public-dns.html\" rel=\"nofollow noopener noreferrer\">2009-12-03\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Conferido em: 2026-10-21\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Cloudflare 1.1.1.1\u003C\u002Fh2>\n\u003Cp>Modo padrão global, sem filtros de ameaças ou conteúdo adulto do Families.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>IPv4: \u003Ccode>1.1.1.1\u003C\u002Fcode>, \u003Ccode>1.0.0.1\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>IPv6: \u003Ccode>2606:4700:4700::1111\u003C\u002Fcode>, \u003Ccode>2606:4700:4700::1001\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>DoH: \u003Ccode>https:\u002F\u002Fcloudflare-dns.com\u002Fdns-query\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>DoT: \u003Ccode>one.one.one.one\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Documentação oficial: \u003Ca href=\"https:\u002F\u002Fdevelopers.cloudflare.com\u002F1.1.1.1\u002Fip-addresses\u002F\" rel=\"nofollow noopener noreferrer\">Cloudflare 1.1.1.1 1\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fdevelopers.cloudflare.com\u002F1.1.1.1\u002Fencryption\u002Fdns-over-tls\u002F\" rel=\"nofollow noopener noreferrer\">Cloudflare 1.1.1.1 2\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fdevelopers.cloudflare.com\u002F1.1.1.1\u002Fencryption\u002Fdns-over-https\u002Fmake-api-requests\u002F\" rel=\"nofollow noopener noreferrer\">Cloudflare 1.1.1.1 3\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Registro público: \u003Ca href=\"https:\u002F\u002Fblog.cloudflare.com\u002Fannouncing-1111\u002F\" rel=\"nofollow noopener noreferrer\">2018-04-01\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Conferido em: 2026-10-21\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Quad9\u003C\u002Fh2>\n\u003Cp>Modo Secure global: bloqueio de domínios maliciosos conhecidos e validação DNSSEC; não é bloqueador completo de anúncios.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>IPv4: \u003Ccode>9.9.9.9\u003C\u002Fcode>, \u003Ccode>149.112.112.112\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>IPv6: \u003Ccode>2620:fe::fe\u003C\u002Fcode>, \u003Ccode>2620:fe::9\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>DoH: \u003Ccode>https:\u002F\u002Fdns.quad9.net\u002Fdns-query\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>DoT: \u003Ccode>dns.quad9.net\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Documentação oficial: \u003Ca href=\"https:\u002F\u002Fdocs.quad9.net\u002Fservices\u002F\" rel=\"nofollow noopener noreferrer\">Quad9 1\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Registro público: \u003Ca href=\"https:\u002F\u002Fuk.newsroom.ibm.com\u002F2017-11-17-IBM-Packet-Clearing-House-and-Global-Cyber-Alliance-Collaborate-to-Protect-Businesses-and-Consumers-from-Internet-Threats\" rel=\"nofollow noopener noreferrer\">2017-11-16\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Conferido em: 2026-10-21\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>AdGuard DNS\u003C\u002Fh2>\n\u003Cp>Modo Default global: filtros de anúncios e rastreadores por regras, separado dos modos sem filtro e familiar.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>IPv4: \u003Ccode>94.140.14.14\u003C\u002Fcode>, \u003Ccode>94.140.15.15\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>IPv6: \u003Ccode>2a10:50c0::ad1:ff\u003C\u002Fcode>, \u003Ccode>2a10:50c0::ad2:ff\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>DoH: \u003Ccode>https:\u002F\u002Fdns.adguard-dns.com\u002Fdns-query\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>DoT: \u003Ccode>dns.adguard-dns.com\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Documentação oficial: \u003Ca href=\"https:\u002F\u002Fadguard-dns.io\u002Fen\u002Fpublic-dns.html\" rel=\"nofollow noopener noreferrer\">AdGuard DNS 1\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Registro público: \u003Ca href=\"https:\u002F\u002Fadguard.com\u002Fen\u002Fblog\u002Fthe-chronicle-of-adguard.html\" rel=\"nofollow noopener noreferrer\">2016-07\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Conferido em: 2026-10-21\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>AliDNS\u003C\u002Fh2>\n\u003Cp>Resolução pública, opção adicional nas redes chinesas conforme a rota real. Não apresentada como filtro completo de anúncios ou conteúdo familiar.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>IPv4: \u003Ccode>223.5.5.5\u003C\u002Fcode>, \u003Ccode>223.6.6.6\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>IPv6: \u003Ccode>2400:3200::1\u003C\u002Fcode>, \u003Ccode>2400:3200:baba::1\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>DoH: \u003Ccode>https:\u002F\u002Fdns.alidns.com\u002Fdns-query\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>DoT: \u003Ccode>dns.alidns.com\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Documentação oficial: \u003Ca href=\"https:\u002F\u002Fwww.alidns.com\u002F\" rel=\"nofollow noopener noreferrer\">AliDNS 1\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fstatic-aliyun-doc.oss-cn-hangzhou.aliyuncs.com\u002Fdownload%2Fpdf%2F176819%2F%25E5%25BF%25AB%25E9%2580%259F%25E5%2585%25A5%25E9%2597%25A8_cn_zh-CN.pdf\" rel=\"nofollow noopener noreferrer\">AliDNS 2\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Registro público: \u003Ca href=\"https:\u002F\u002Fdocs-aliyun.cn-hangzhou.oss.aliyun-inc.com\u002Fpdf\u002Falidns-faqs-cn-zh-2019-05-24.pdf\" rel=\"nofollow noopener noreferrer\">2019-05-24\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Conferido em: 2026-10-21\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>DNSPod \u002F Tencent Public DNS\u003C\u002Fh2>\n\u003Cp>Resolução pública gratuita, opção adicional na China sem regras personalizadas pagas. A lista oficial contém atualmente um endereço IPv4. Não apresentada como filtro familiar.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>IPv4: \u003Ccode>119.29.29.29\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>IPv6: \u003Ccode>2402:4e00::\u003C\u002Fcode>, \u003Ccode>2402:4e00:1::\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>DoH: \u003Ccode>https:\u002F\u002Fdoh.pub\u002Fdns-query\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>DoT: \u003Ccode>dot.pub\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Documentação oficial: \u003Ca href=\"https:\u002F\u002Fmain.qcloudimg.com\u002Fraw\u002Fdocument\u002Fproduct\u002Fpdf\u002F302_110810_cn.pdf\" rel=\"nofollow noopener noreferrer\">DNSPod \u002F Tencent Public DNS 1\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Registro público: \u003Ca href=\"https:\u002F\u002Fdocs.dnspod.cn\u002Fdns\u002Fcheck-effective\u002F\" rel=\"nofollow noopener noreferrer\">2021-10-15\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Conferido em: 2026-10-21\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Yandex DNS\u003C\u002Fh2>\n\u003Cp>Modo Basic para Rússia e redes próximas, sem filtros Safe ou Family. O campo DoH apresenta o nome de servidor publicado oficialmente.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>IPv4: \u003Ccode>77.88.8.8\u003C\u002Fcode>, \u003Ccode>77.88.8.1\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>IPv6: \u003Ccode>2a02:6b8::feed:0ff\u003C\u002Fcode>, \u003Ccode>2a02:6b8:0:1::feed:0ff\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>DoH (nome do servidor): \u003Ccode>common.dot.dns.yandex.net\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>DoT: \u003Ccode>common.dot.dns.yandex.net\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Documentação oficial: \u003Ca href=\"https:\u002F\u002Fdns.yandex.com\u002F\" rel=\"nofollow noopener noreferrer\">Yandex DNS 1\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Registro público: \u003Ca href=\"https:\u002F\u002Fyandex.ru\u002Fblog\u002Fsafesearch\u002F959\" rel=\"nofollow noopener noreferrer\">2013-04-09\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Conferido em: 2026-10-21\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Saiba mais\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Ca href=\"\u002Fpt-br\u002Flearn\u002Fwhat-is-dns\u002F\">O que é DNS e como ele encontra um endereço IP?\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"\u002Fpt-br\u002Flearn\u002Fdoes-changing-dns-improve-speed\u002F\">Trocar o DNS deixa a internet mais rápida ou reduz o ping?\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwww.rfc-editor.org\u002Frfc\u002Frfc8484\" rel=\"nofollow noopener noreferrer\">DNS over HTTPS — RFC 8484\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwww.rfc-editor.org\u002Frfc\u002Frfc7858\" rel=\"nofollow noopener noreferrer\">DNS over TLS — RFC 7858\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n",1793192131249]