paulmillr/encrypted-dns

DNS over HTTPS config profiles for iOS & macOS

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 44 minutes ago
Type:Configuration / DotfilesCategory(s):Privacy & CryptographySecurity & Privacy
Added to GitGenius on September 14th, 2026
Created on September 17th, 2020
Open Issues & Pull Requests: 10 (+0)
GitHub issues: Enabled
Number of forks: 434
Total Stargazers: 4,821 (+0)
Total Subscribers: 68 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.6 hours
Mean response time: 101.5 days
90th percentile: 352.4 days
Tracked items: 43

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 8
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 802 days
Stale 30+ days: 7
Stale 90+ days: 4

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • apple bug (2)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

encrypted-dns is a collection of DNS over HTTPS and DNS over TLS configuration profiles for iOS and macOS.

The tool addresses the need to route DNS queries through encrypted channels rather than unencrypted DNS, preventing ISPs and network operators from observing which domains a user visits. It provides ready-made configuration profiles in the mobileconfig format that users can download and install directly on their devices. The profiles configure encrypted DNS providers including Cloudflare, Google, OpenDNS, and Quad9, implementing the DNS over HTTPS and DNS over TLS standards.

Users should choose this tool if they want to enable encrypted DNS on Apple devices without manually configuring DNS settings. It suits anyone seeking privacy from network-level DNS observation, whether on personal iPhones, iPads, or Macs. The tool is particularly valuable for users who lack technical expertise to configure DNS over TLS or HTTPS through other means, since installation requires only downloading a profile and following the system settings prompts. The README distinguishes between providers that perform censorship or filtering and those that do not, helping users select based on their filtering preferences.

The project accepts contributions for adding new providers or editing existing ones, indicating openness to community expansion of the provider list. Development activity centers on maintaining the configuration profiles themselves rather than building complex software infrastructure.