Finding: Invalid IP Address
This finding means your domain resolves to an IP address in a range that cannot legitimately serve your site — a 127.x.x.x loopback address or a 0.x.x.x address. This is a DNS misconfiguration, not intended behavior.
Last updated August 11, 2026.
What it means
127.0.0.0/8is the loopback range — it always means "this same machine," not a real destination on the internet. 0.0.0.0/8 is a reserved range that no host can legitimately use either. If your domain's A record resolves to an address in either range, visitors and mail servers cannot reach your actual server through it.
Why it matters
This pattern almost always comes from a leftover placeholder value — a template DNS record that was never replaced with the real server IP, a local development configuration accidentally pushed to production DNS, or a scripted DNS update that failed partway and wrote a default value. The practical effect ranges from the domain simply not loading, to loading inconsistently depending on caching, to browsers resolving it to a visitor's own machine.
What Nivaronix checks
After resolving your domain, Nivaronix checks whether the returned IP address begins with 127. or 0.. This finding fires only for those two ranges — it is not a broader check of every reserved or private IP block.
Example evidence (illustrative — not live scan data)
Hostname: example.com -> 127.0.0.1
How to fix it
- Find the actual public IP address of the server or load balancer that should be serving this domain, from your hosting or cloud provider's dashboard.
- At your DNS host, open the A record (and AAAA record, if you have one) for the affected hostname.
- Replace the loopback or reserved-range value with the correct public IP address.
- Check any automation (CI/CD scripts, infrastructure-as-code templates) that writes this record, so the placeholder doesn't get written back on the next deploy.
How to verify the fix
Re-run the DNS security checker and confirm your domain now resolves to your real server's public IP address.