Public DNS resolver · Canadian Internet Registration Authority (CIRA)

CIRA Canadian Shield DNS servers

CIRA Canadian Shield (run by Canadian Internet Registration Authority (CIRA)) answers on 149.112.121.10 and 149.112.122.10, with DNS over HTTPS at https://private.canadianshield.cira.ca/dns-query. In our 2026-09-24 test it did not validate DNSSEC and sent no client subnet.

Addresses
12
Variants
3
Measured
2026-09-24
Primary IPv4
149.112.121.10
All IPv4
149.112.121.10, 149.112.122.10, 149.112.121.20, 149.112.122.20, 149.112.121.30, 149.112.122.30
All IPv6
2620:10A:80BB::10, 2620:10A:80BC::10, 2620:10A:80BB::20, 2620:10A:80BC::20, 2620:10A:80BB::30, 2620:10A:80BC::30
DNS over HTTPS
https://private.canadianshield.cira.ca/dns-query, https://protected.canadianshield.cira.ca/dns-query, https://family.canadianshield.cira.ca/dns-query
DNS over TLS
private.canadianshield.cira.ca, protected.canadianshield.cira.ca, family.canadianshield.cira.ca
Service variants
3 (Canadian Shield Private; Canadian Shield Protected; Canadian Shield Family)
DNSSEC in our test
Does not validate
Client subnet (ECS)
None sent
Protocols
DNS (53), DoT, DoH
Jurisdiction (stated)
As a national not-for-profit, CIRA will never sell your personal data or use it to show you ads.

CIRA Canadian Shield DNS addresses by variant

Set the IPv4 or IPv6 addresses as your DNS servers, or use an encrypted endpoint where one is listed.
CIRA Canadian Shield addresses
VariantFiltering (operator description)IPv4IPv6Encrypted
Canadian Shield PrivateNot specified by the operator149.112.121.10149.112.122.102620:10A:80BB::102620:10A:80BC::10DoH https://private.canadianshield.cira.ca/dns-queryDoT private.canadianshield.cira.ca
Canadian Shield ProtectedMalware, phishing, botnets and online scams149.112.121.20149.112.122.202620:10A:80BB::202620:10A:80BC::20DoH https://protected.canadianshield.cira.ca/dns-queryDoT protected.canadianshield.cira.ca
Canadian Shield FamilyEverything in Protected, plus adult content149.112.121.30149.112.122.302620:10A:80BB::302620:10A:80BC::30DoH https://family.canadianshield.cira.ca/dns-queryDoT family.canadianshield.cira.ca

What we observed

Measured 2026-09-24 from one vantage point, three rounds per address, majority result. Anycast resolvers can behave differently from other networks.
DNSSEC validation
Does not validate Returned addresses for dnssec-failed.org, rhybar.cz and badsig.go.dnscheck.tools, which a validating resolver would refuse.
Client subnet (ECS)
No client subnet reached the authoritative server from any address we probed.
Plain DNS and NXDOMAIN
6/6 documented IPv4 addresses answered on port 53. Random non-existent names came back as NXDOMAIN, so errors are not rewritten into ads or search pages.
Encrypted endpoints
ProtocolEndpointOur test query
DoHhttps://private.canadianshield.cira.ca/dns-queryAnswered
DoHhttps://protected.canadianshield.cira.ca/dns-queryAnswered
DoHhttps://family.canadianshield.cira.ca/dns-queryAnswered
DoTprivate.canadianshield.cira.caAnswered
DoTprotected.canadianshield.cira.caAnswered
DoTfamily.canadianshield.cira.caAnswered

Which networks carry it

The announcing network comes from RIPEstat routing data for each documented address. The query network is where the resolver sent its own lookups during our probe, which a DNS leak test reports.
Networks
ASNHolderRole
AS40568CIRADNS3 - CIRA Canadian Internet Registration Authority Autorit Canadienne pour les enregistrements InternetAnnounces the service addresses
AS5645TEKSAVVY - TekSavvy Solutions, Inc.Queried from, in our probe
AS55195CIRA-CLOUD1 - CIRA Canadian Internet Registration Authority Autorit Canadienne pour les enregistrements InternetQueried from, in our probe

Operator statements

Quoted from the operator's pages and checked word for word. We have not audited these practices.
“As a national not-for-profit, CIRA will never sell your personal data or use it to show you ads.”
www.cira.ca

Confirm your device is using CIRA Canadian Shield

Changing a DNS setting does not guarantee your lookups reach that resolver: a VPN, a browser's own secure DNS or a proxy can send them elsewhere. Our DNS leak test shows which resolvers actually received your queries.
From a terminal
# Which address did the resolver query from?
dig +short whoami.akamai.net @149.112.121.10

# Does it pass your subnet on (ECS)?
dig +short TXT o-o.myaddr.l.google.com @149.112.121.10

# Does it validate DNSSEC? SERVFAIL means yes
dig dnssec-failed.org @149.112.121.10

Behind a proxy

With an HTTP proxy, or a client set to socks5h://, the proxy side resolves hostnames, so your own resolver setting does not apply to that traffic. With socks5:// in curl or Python requests, your device resolves names first. The SOCKS5 vs SOCKS5h guide shows how to check which one you have.

CIRA Canadian Shield questions

What are CIRA Canadian Shield's DNS server addresses?
Canadian Shield Private: 149.112.121.10, 149.112.122.10, 2620:10A:80BB::10, 2620:10A:80BC::10. Canadian Shield Protected: 149.112.121.20, 149.112.122.20, 2620:10A:80BB::20, 2620:10A:80BC::20. Canadian Shield Family: 149.112.121.30, 149.112.122.30, 2620:10A:80BB::30, 2620:10A:80BC::30.
Does CIRA Canadian Shield validate DNSSEC?
Not in our 2026-09-24 test: it returned addresses for all three deliberately mis-signed domains.
Does CIRA Canadian Shield support DNS over HTTPS or DNS over TLS?
DoH: https://private.canadianshield.cira.ca/dns-query, https://protected.canadianshield.cira.ca/dns-query, https://family.canadianshield.cira.ca/dns-query. DoT: private.canadianshield.cira.ca, protected.canadianshield.cira.ca, family.canadianshield.cira.ca. 6 of 6 answered our test query on 2026-09-24.
Does CIRA Canadian Shield send my IP subnet to other servers (ECS)?
We observed no client subnet on any address we probed.
How can I check that I am using CIRA Canadian Shield?
Run a DNS leak test and compare the network it reports with the one CIRA Canadian Shield queried from in our probe (AS5645, AS55195). On the command line, dig +short whoami.akamai.net @149.112.121.10 returns the address the resolver used to query Akamai.

Sources

Addresses and endpoints come from each operator's documentation; behaviour is what we measured from one location on 2026-09-24. Speed, uptime and how well a filter blocks what it promises were not tested.