A Filtering Error at Orange Blocks example.com, an IANA-Reserved Domain

Blocked DNS lookup shown on a developer's terminal screen

A domain that’s part of the internet’s basic infrastructure, example.com, is showing up blocked “at the request of the competent authority” for some Orange customers in Spain. The domain belongs to IANA, has been reserved since 1999 for documentation purposes, and hosts no content, so everything points to an error in the operator’s filtering systems. For development and systems teams, the case is a reminder of how fragile mass DNS or IP blocking can be.

The example.com block in 20 seconds

  • example.com shows a court-order blocking notice to some Orange customers.
  • It’s an IANA domain reserved under RFC 2606 for examples and documentation.
  • The likely cause is a misconfiguration in the operator’s filters.
  • It can affect tests, scripts, and development environments that use that domain.

As Teléfonos.es explains in its report on the block, based on a notice from Bandaancha, the message users see is the one Orange normally uses for domains subject to court orders against piracy. Orange hasn’t explained why example.com is on that list, and the block doesn’t affect all of its customers.

Why example.com Is Special

RFC 2606, from 1999, reserved example.com, example.net, and example.org for use in documentation, manuals, and examples without any risk of pointing to a real third-party site. They’re managed by IANA, the authority that coordinates the DNS root zone, the allocation of IP addresses and autonomous system numbers to regional registries, and the protocol parameter registries. Many scripts, containers, and connectivity tests use example.com specifically to check that there’s internet access or that DNS resolution is working.

What a Systems Team Should Check

If a health check or an automated test uses example.com and runs from an Orange connection, it can fail for no apparent reason: the operator’s DNS returns the blocking page instead of the expected response. It’s good practice not to rely on a single external domain for these checks, to use controlled DNS resolvers in production and CI environments, and, when a test domain that doesn’t need to reach the internet is needed, to use the names reserved for internal use, such as .test, .invalid, or .localhost, also defined in RFC 2606.

The case adds to others in which court-ordered blocks by Spanish operators have hit legitimate services — for example, by blocking IP addresses shared across content delivery networks, a pattern we looked at in our explainer on how internet blocking in Spain works, why it fails, and who gets caught in the crossfire. Bandaancha presents it as further proof that the filters overreach due to configuration errors, to the detriment of net neutrality.

Frequently Asked Questions

Why is example.com blocked on Orange?

Orange hasn’t explained it. Everything points to an error in its filters, perhaps from using the domain in tests.

Can it affect my scripts or tests?

Yes — if they use example.com and resolve through Orange’s DNS, they can get the blocking page instead of the expected response.

What domains should I use for internal testing?

The ones reserved for that purpose under RFC 2606, such as .test, .invalid, or .localhost.

Sources:

This article is also available in Spanish: “Un error de filtrado bloquea example.com, dominio reservado de IANA,” on revistacloud.com.

Scroll to Top