CloudFlare ByPasses Options

It depends on what you mean by "bypass Cloudflare DNS" — here are the most common scenarios:

1. Reaching the Origin Server (bypassing Cloudflare's proxy/CDN)

If a site is behind Cloudflare's orange-cloud (proxied) DNS records, you want the real server IP:

• Check non-proxied subdomains – Sometimes mail.example.com or ftp.example.com point directly to the origin IP (grey cloud in the DNS panel).
• DNS history lookups – Services like SecurityTrails, DNSDumpster, or ViewDNS.info can show past A/CNAME records before Cloudflare was added.
• SSL Certificate Transparency logs – Check crt.sh or Censys for the domain; sometimes the origin IP appears in related certs.
• Direct IP + Host header – Once you find the origin IP, you can curl it:

  curl -H "Host: example.com" http://<origin-ip>
  

• dig / nslookup – Look for A records that aren't Cloudflare IPs (104.x, 172.67.x, 188.x, etc.).

2. Using a Different DNS Resolver (instead of 1.1.1.1)

If you just want to stop using Cloudflare's public DNS:

Change it in your OS settings, router DHCP config, or in a browser like Firefox (Settings → Network → DNS over HTTPS).

3. Getting Past Cloudflare's Anti-Bot / Challenge Pages

If you're hitting a "Checking your browser…" or 403 page:

• Use a real, non-headless browser with JS enabled.
• Clear cookies / try a different browser or private window.
• Wait a few seconds for the JS challenge to resolve.
• For developers/owners: adjust the Security Level, WAF rules, or use Cloudflare Turnstile / API tokens.
• For scraping: use a residential proxy + a real browser fingerprint (e.g., Playwright with stealth patches), or hit the site's API endpoint directly if one exists.

Which of these are you actually trying to solve? I can give more specific steps if you share a bit more context.