Determining the age of a domain
Posted: Thu Feb 06, 2025 9:01 am
IANA and registrars are not responsible for and have no control over the use of domains.
The age of a domain is determined by an entry in an Internet registry that is managed by a top-level domain (TLD) registrar. The registrar is ultimately responsible for registering the domain and updating the relevant data. The registry entry indicates the date the domain was originally created, but this only changes if it is re-registered after its expiration date. For this reason, domain age is an extremely imprecise indicator of when a particular resource has begun active operation.
Another problem is that the filter may know only macedonia mobile database IP address of the destination host when it makes a decision. For example, this might happen when filtering the first packet sent to a particular destination (TCP SYN or the first UDP packet of another network or transport layer protocol). One way to find out the destination domain is a reverse DNS lookup, but the host domain may not match the domain that was originally sent for resolution. In this case, the domain age is a useless parameter.
For example, the current resolution of is 172.224.15.98. The reverse resolution of this IP address is a172-224-15-98.deploy.static.akamaitechnologies.com. The mcafee.com domain was registered on 8/5/1992, and the akamaitechnologies.com domain was registered on 8/18/1998. However, the fact that the long-established mcafee.com domain is hosted by the long-established akamaitechnologies.com domain does not provide any indication of when the destination or 172.224.15.98 became active, or whether there are any risks associated with communicating with this IP address. Domain age becomes even less useful when we're dealing with destinations hosted in the public cloud (IaaS and SaaS) and using provider domains.
The age of a domain is determined by an entry in an Internet registry that is managed by a top-level domain (TLD) registrar. The registrar is ultimately responsible for registering the domain and updating the relevant data. The registry entry indicates the date the domain was originally created, but this only changes if it is re-registered after its expiration date. For this reason, domain age is an extremely imprecise indicator of when a particular resource has begun active operation.
Another problem is that the filter may know only macedonia mobile database IP address of the destination host when it makes a decision. For example, this might happen when filtering the first packet sent to a particular destination (TCP SYN or the first UDP packet of another network or transport layer protocol). One way to find out the destination domain is a reverse DNS lookup, but the host domain may not match the domain that was originally sent for resolution. In this case, the domain age is a useless parameter.
For example, the current resolution of is 172.224.15.98. The reverse resolution of this IP address is a172-224-15-98.deploy.static.akamaitechnologies.com. The mcafee.com domain was registered on 8/5/1992, and the akamaitechnologies.com domain was registered on 8/18/1998. However, the fact that the long-established mcafee.com domain is hosted by the long-established akamaitechnologies.com domain does not provide any indication of when the destination or 172.224.15.98 became active, or whether there are any risks associated with communicating with this IP address. Domain age becomes even less useful when we're dealing with destinations hosted in the public cloud (IaaS and SaaS) and using provider domains.