Welcome to dns4.cc!

dns4.cc logo

Welcome! We’re so happy you’re here, and we want you to know that we care about your digital footprint and data anonymity. We learn from your online habits to help you stay safe and secure. At the end of the day, you’re the expert when it comes to what you choose to reveal or share. We’re here to support you with our technology, experience, and knowledge. With dns4.cc DNS servers, you’re in good hands.

“Freedom is like the future. We all deserve it, but we have to want it to come to us.”^*

^{* citation by darkmark, feel free to use & spread it!:)}

TL;DR for geeks – github repo is here :)

!!! NO google NOR cloudflare !!!

We proudly guarantee that our servers are in no way connected to the BIG BROTHERS of 8.8.x.x or 1.x.x.1. They are not and will never be part of these INTERNET CRIMINALS!

All of our servers are exclusively controlled by us and only by us.

🆕 Ladies and gentlemen, good NEWS! 🆕

Apr-20–2025 - Happy Easter!

Apr-20–2025 - We add the third Kairos/NTP server – 🇸🇬 singapore.kairos.monster (167.253.159.205, 2a11:8083:11:1106::79).

Apr-13–2025 – The first two Kairos server are online! If you live in the middle of Europe or in between the Big Lakes, you’re in luck. 🇨🇿 time.k2211.cz (194.182.84.241, 2001:15e8:110:7d00::396) and 🇺🇸 buffalo.kairos.monster (64.44.115.65, 2001:15e8:110:7d00::396) are there at your NTP service.

Mar-17–2025 - We are about to launch a brand new project called “Kairos”. Kairos is a network of NTP servers (time servers) distributed around the globe using the dns4.cc infrastructure. Stay tuned for more details!

Feb-25–2025 – We are running two new TOR bridges in Europe (located in 🇨🇿 and 🇸🇰) and that’s it.

Jan‑8–2025 – dns4.cc-us-ny-* 🇺🇸 has been moved as Buffalo, NY » Ashburn, VA and renamed to dns4.cc-us-va-* It’s much more faster now.

Dec-25–2024 - dns4.cc-us-ny-* 🇺🇸 will be changed to dns4.cc-us-va-* and moved to Ashburn/VA soon!

Dec-16–2024 - dns4.cc-de-* in 🇩🇪 is back!

Dec-13–2024 – Let us kindly introduce the new node in 🇸🇬! We add new node in Singapore, it’s in beta regime now, but feel free to test it! It runs on OVH cloud and its names are dns4.cc-sg-ipv4, dns4.cc-sg-ipv6, anon-dns4.cc-sg-ipv4 and anon-dns4.cc-sg-ipv6. Enjoy the new node in an Asian business capital and let us know your experiences.

Sep‑7–2024 – Big in 🇯🇵, great song by Alphaville, I’m wondering if you remember how great this song by Alphaville was. We were teenagers then, but now it’s going to be true! dns4.cc crew will soon introduce new dns4.cc-jp-ipv4 & dns4.cc-jp-ipv6 nodes. It’s located near the holy Mt. Fuji, which is a very special place. Check the map, circle around the globe then closes. Expected launch date in September 2024.

Jun‑1–2024 – We’re thrilled to announce that dns4.cc-cz is back and better than ever! Thanks to our friends in Prague 🇨🇿, we’ve reincarnated dns4.cc-cz & anon-dns4.cc-cz! It’s finally back, and it’s better, cooler, and stronger than ever. Now it supports both IPv4 and IPv6, and it’s in beta mode. We’d love for you to test it as much as possible to prove connectivity and stability.

A big thank you to Marek (he knows…) for handling the negotiations, translating, and being so welcoming. We had the most incredible, unforgettable couple of days in the most beautiful, ancient city of Prague… 🍺🍺🍺 🇨🇿 😎

Personally, we are strong believers in FREEDOM and the basic human right to remain anonymous and untraceable if you choose so.

Respecting this fact, all dns4.cc resolvers & anonymizing relays were, are, and always will be:

PUBLIC & FREE TO USE
SECURED BY DNSSEC
NON‐BLOCKING
NON‐LOGGING
NON‐FILTERED

All servers would be used as DNSCrypt public resolvers and/or anonymizing relays.

We mainly use GreenCloud vps for their affordability, great support and open minded approach, use our referral link to give them a try.

Before we get started, it’s nice to keep in mind a few really basic reminders about how to behave in a binary world:

It’s OK to be suspicious, suspicious and one more time suspicious and cautious in every way possible.
It’s okay to use only proven tools or software (I don’t want to push you into a corner, but DNS servers provided by dns4.cc are the best choice 😆).
It’s normal to consider your data and digital security and/or anonymity as a treasure.
ACABs(👮), 🕵️, hackers, 🤖 and other whatever suckers never sleep and are at least one step ahead…
This fight should NEVER be over.
It’s generally getting worse by the minute.
At the end of the day, you’re the only one responsible for your digital anonymity and security.

And finally how to 🏁

To start using our network simply add the lists of dns4.cc servers and anonymization relays to your dnscrypt-proxy.toml config, restart the service and enjoy.

Right, we boldly assume that you already have dnscrypt‐proxy installed on your 💻 and/or 📱. 😉 If not, visit the dnscrypt‐proxy repo for more details and return back when you are done. Principles of operating, theory, technical details and other useful stuff can be found at the DNSCrypt website.

It’s easy as:

Either download dns4.cc repository as ZIP or clone it to anywhere like:
This step is not absolutely necessary, the resolvers will also work if you just add them to the dnscrypt-proxy.toml file as shown below, because it automatically fetches the list from github. If you don’t want to play with the config locally or contribute to the project, just skip to the next step.
```
git clone https://github.com/drkmark/dns4.cc.git
```

and copy all the files to dnscrypt‐proxy working directory (i.e. /opt/dnscrypt‐proxy/).

In [sources] section of your dnscrypt-proxy.toml configuration file you should add something like (these aren’t an options, you should do both):

a. dns4.cc public resolvers

[sources.‘dns4.cc-resolvers.md’]
    urls = [‘https://raw.githubusercontent.com/drkmark/dns4.cc/main/dns4.cc-resolvers.md’]
    cache_file = ‘dns4.cc-resolvers.md’
    minisign_key = ‘OUR‐PUBLIC‐MINISIGN‐KEY‐GOES‐HERE’
    refresh_delay = 72

b. dns4.cc anonymizing relays

[sources.‘dns4.cc-relays.md’]
    urls = [‘https://raw.githubusercontent.com/drkmark/dns4.cc/main/dns4.cc-relays.md’]
    cache_file = ‘dns4.cc-relays.md’
    minisign_key = ‘OUR‐PUBLIC‐MINISIGN‐KEY‐GOES‐HERE’
    refresh_delay = 72

In [anonymized_dns] section then add routes as needed, i.e. (or as you wish):

[anonymized_dns]
routes = [
    { server_name=‘dns4.cc-us-ca-ipv4’, via=[‘anon-dns4.cc-us-va-ipv4’], via=[‘anon-dns4.cc-us-tx-ipv4’] },
    { server_name=‘dns4.cc-vn-ipv6’, via=[‘anon-dns4.cc-hk-ipv6’], via=[‘anon-dns4.cc-sg-ipv6’] },
    .….
    ]

Btw. it’s not necessary to be “superanonymized” over more than 1–2 relays, as the latency would increase dramatically. Just check and play with routes to test the latency, e.g. with DNS leak script from @macvk.

Read “/your/dncrypt‐proxy/working‐directory/“example-dnscrypt-proxy.toml for proper settings!

list of dns4.cc public resolvers
list of dns4.cc anonymization relays
minisign key should be taken ONLY from our github repo - Don’t underestimate it, please. We sign every new commit to be absolutely sure that all servers used are authentic and secure.

DNS servers locations as of January 2025:

Americas

San Jose, CA 🇺🇸
Dallas, TX 🇺🇸
Ashburn, VA 🇺🇸

EMEA

Coventry, UK 🇬🇧
Frankfurt Am Main, Germany 🇩🇪
Budweis, Czechia 🇨🇿
Bratislava, Slovakia 🇸🇰

APAC

Ho Chi Minh City, Vietnam 🇻🇳
Hong Kong, China 🇨🇳
Tokyo, Japan 🇯🇵
Singapore 🇸🇬

…and that’s all, folks. have a good time!

If you have any questions or comments, we’re all ears. Send them our way at crew(at)dns4.cc.

dns4cc logo