Is Level3 / Lumen Secure?
Independent privacy and security audit of Level3 / Lumen DNS servers, with live monitoring data.
Last updated March 26, 2026
Level3 / Lumen passes some security checks but is missing support for certain features. Review the details below.
Security Audit Results
| Check | Result | Details |
|---|---|---|
| DNSSEC Validation | No | Does not validate DNSSEC. Vulnerable to DNS cache poisoning attacks. |
| NXDOMAIN Hijacking | No | Returns proper NXDOMAIN responses for non-existent domains. |
| DNS-over-TLS (DoT) | Not supported | DNS queries are sent in plain text over this protocol. |
| DNS-over-HTTPS (DoH) | Not supported | No DoH endpoint available. |
| Logging Policy | Unknown retention policy | |
| Reliability | 96% | Based on continuous monitoring from our probe network. |
Level3 / Lumen DNS Addresses
| Type | IP Address | |
|---|---|---|
| Primary | 4.2.2.1 |
|
| Secondary | 4.2.2.2 |
Test Level3 / Lumen Yourself
Run a live privacy and security check on 4.2.2.1 from your location. Get DNSSEC, NXDOMAIN, encryption, and latency results in seconds.
Run Privacy Check on 4.2.2.1How Level3 / Lumen Compares
See security audits for other DNS providers:
Related Guides
Frequently Asked Questions
Is Level3 / Lumen safe to use?
Level3 / Lumen passes some security checks but lacks support for certain features like encrypted DNS or DNSSEC. It is adequate for basic use but privacy-conscious users may want a more feature-complete provider.
Does Level3 / Lumen log DNS queries?
Level3 / Lumen logging policy: Unknown retention policy. Always review the provider's current privacy policy for the latest details.
Does Level3 / Lumen support encrypted DNS?
Level3 / Lumen does not support encrypted DNS (neither DoT nor DoH). Your DNS queries travel in plain text and can be monitored by your ISP.
How reliable is Level3 / Lumen?
Level3 / Lumen (4.2.2.1) has a reliability score of 96% based on our continuous monitoring. This is excellent uptime.
What are the DNS addresses for Level3 / Lumen?
Primary: 4.2.2.1, Secondary: 4.2.2.2. Configure both for redundancy.