A customer clicks an old bookmark for your spring promotion. The promotion has ended, and you stopped paying for the page months ago. What should the customer see now? Perhaps a short explanation on a page you still control. Perhaps the name should no longer lead anywhere. What you do not want is to have forgotten where it sends them.
A company can cancel a service while leaving the instructions that send visitors to it unchanged. Microsoft describes how a DNS record — an entry in the internet’s naming system — can outlive the rented service it points to. If the platform lets someone else take over that destination, visitors may be sent to the new occupant. This is one way a subdomain takeover can happen. A broken link alone does not show that it is possible. 12
The name and the rented service are separate
Start with the name. If a business uses bakery.example, a more specific name such as spring.bakery.example is a subdomain. It can identify a separate service, even though customers recognize it as part of the same business name. The Domain Name System, or DNS, provides information that helps computers find the destination for that name. 1
The bakery might put the promotion on an outside platform. Its DNS can contain an alias: an instruction that this name refers to another name. The record used for that is called CNAME. The customer remembers the bakery’s name; the lookup follows the alias toward the platform. The DNS record and the platform subscription are separate pieces of the arrangement. 1 2
Follow an old bookmark while the campaign is still running. The browser is the customer’s program for displaying pages. The device asks a DNS lookup helper how to reach spring.bakery.example. The helper finds the bakery’s alias, follows the platform name and obtains a network address. The browser can then contact the platform and request the page. The platform has an arrangement associating the bakery’s name with the bakery’s campaign. That association is needed as well as the DNS direction. 1 12
Notice what the customer’s device did not ask: “Has the bakery paid its subscription this month?” DNS answers from published records. It does not read the bakery’s cancellation email or automatically discover the business decision that the campaign is over. The people or systems responsible for retiring the service must coordinate the change in the platform with the change in the naming information. 1 12
Now the promotion ends. Cancelling the subscription does not necessarily remove the bakery’s DNS record. It is like leaving an old forwarding address in an address book after moving out. The instruction still exists, although the intended service has gone. 12
When an old instruction can become dangerous
For a takeover to be possible, more must happen than a page disappearing. The platform must allow the relevant destination or domain binding to come under someone else’s control, and the old reference must still lead traffic there. A domain binding is the platform’s association between a customer’s web name and the service that should answer for it. Rules for creating that association matter. 12
The sequence matters. First the bakery releases the old service. Next the stale DNS reference remains available to anyone who looks up the campaign name. If the platform’s rules allow a different account to acquire the relevant destination and serve the bakery’s custom name, that account may now answer requests from the old bookmark. The bakery has not necessarily lost registration of its main domain. The problem is that a name still under its control directs visitors toward a service it no longer controls. 12
This can make misleading content particularly convincing: the customer began with the bakery’s familiar name, not a visibly unrelated address. Whether an attacker can obtain that particular platform arrangement depends on the platform’s safeguards and the remaining configuration. Some unused targets cannot be claimed this way. Keeping those conditions explicit prevents us from turning every cancelled subscription into a confirmed takeover. 12
Some services verify that a customer is entitled to use the domain before accepting the association. Microsoft describes such a protection for Azure App Service: a domain-verification record can prevent another account from attaching the custom name. This is why a behavior documented for one platform cannot simply be assumed for every other platform or service. 12
A page saying “application not found” is therefore a clue, not proof of takeover. It shows that a request did not receive the intended application. It does not establish whether another person could attach the name, much less that someone already has. There are three different questions: is the reference obsolete, is it claimable by someone else, and has someone actually taken control?
Even if claimability has not been established, the obsolete reference can still deserve cleanup. The bakery does not need to demonstrate an attack before deciding that a closed promotion should stop depending on a cancelled account. It needs to understand the intended outcome and arrange a safe change.
Close the route as well as the subscription
Before deleting the service, decide what should happen to its public name. If old leaflets or bookmarks may still be used, a page under your control explaining that the promotion ended can be more helpful than an unexplained error. If the name is no longer needed, its obsolete DNS reference can be removed. The important point is to avoid releasing a destination while still deliberately directing customers to it. DNS cleanup belongs in service retirement. 12
The timing needs care. DNS lookup systems can keep answers temporarily in a saved store called a cache. Each record includes a permitted reuse time, known as TTL. Removing or changing the original record does not immediately erase those saved answers. The administrator should account for previously published lifetimes when deciding when the old resource can safely be released. There is no universal waiting period that fits every arrangement. 1 2
For example, the administrator first points the campaign name to a replacement page that the bakery controls. An office lookup helper that already saved the old answer may still send a visitor toward the original platform until that answer’s permitted reuse time has run out. Keeping the old resource controlled while the change takes effect avoids deliberately releasing it while these ordinary saved directions may still be used. Lowering a lifetime now does not retrospectively shorten the lifetime of a copy saved earlier. 1 2 12
If the bakery removes the name instead, the desired result is a failed lookup rather than an attacker-controlled page. A notice saying the campaign ended requires a working web service to produce that notice; merely deleting the DNS entry does not create a helpful explanatory page. The business needs to choose its intended result, and the administrator can then implement the naming and service changes that produce it. 1 12
Also consider where the name appears: old buttons, application settings and message templates may still send people or software to it. Removing a DNS record does not rewrite those references. Microsoft’s cleanup guidance specifically includes reviewing outdated application references and investigating possible compromise where appropriate. 12
A broken campaign page is not the whole company
If a page unexpectedly shows someone else’s content, stop treating the issue as ordinary housekeeping. Preserve what was observed and contact the people responsible for the service so they can investigate. Whether any customer information was exposed depends on what actually used that name and what happened; it cannot be settled from the name alone. 12
Likewise, a forgotten promotion does not by itself establish access to the company’s invoice archive or other services. It may prompt a reasonable question about how temporary services are closed, but the relationship to those other systems still has to be shown. Do not try to settle uncertainty by registering someone else’s apparently abandoned resource. That changes the situation and needs explicit authorization.
Before cancelling the next campaign service, agree what an old bookmark should do: reach a replacement page you control, or stop leading to the retired service. Ask the administrator to arrange that change before releasing the old destination.
Sources
12 — Microsoft Learn — Prevent dangling DNS entries and avoid subdomain takeover
1 — RFC 1034 — Domain names: concepts and facilities
2 — RFC 1035 — Domain names: implementation and specification