
While new domains can be created for perfectly innocent purposes, the sad reality is that new domains are often created to facilitate nefarious activities. As a result, cybersecurity people often view new domains with suspicion, at least until their trustworthiness has been carefully scrutinized and found to be satisfactory.
Given that reality, there’s been a lot of interest in four of Farsight’s products:
But what’s the difference between the four? And how do they differ from some of the “Newly Registered” domain products other security companies may tout? Let’s get that last question out of the way first.
The key difference between Farsight’s NOD/NOH/NAH products and the “newly registered” products that some other vendors may offer is that Farsight focuses on what we’ve actually SEEN in LIVE DNS data from our sensor operators, NOT what may show up as “newly registered” in some once-a-day report from TLD operators. This is important for three reasons:
Because Farsight watches for new domains in live network traffic, we can alert subscribers to the existence of new domains as soon as they’re seen, thereby allowing you to take steps to protect yourself from these “no-huddle-offense” domains immediately, not after nearly a day of abuse has already happened.
Because Farsight WATCHES for domain USE rather than for merely relying on domain CREATION reports, we don’t care if a domain is created and then left completely domant for months before it is eventually used — we pay attention to ALL domains when we initially see them used.
The next dimension to understand when thinking about all these “newly ________” products is “Do they refer to effective second-level domains (aka “delegation points”) or hostnames (aka”Fully Qualified Domain Names (FQDNs)”)? In Farsight’s case, this is the difference between:
When a person or company purchases a domain from a registrar, the domain name they buy is technically known as a “delegation point” or “base domain name.” Technically, we track effective 2nd level domains, as defined by the Public Suffix List [(PSL) .] For instance, the name example.com would be a “delegation point.” That’s what we track in NOD.
When a domain owner creates a name for a computer under that delegation point (such as www.example.com) that’s often called a “hostname” or a “fully qualified domain name” (“FQDN”). That’s what we track in NOH.
We offer feeds of BOTH newly seen domain names (NOD) and newly seen FQDNs (NOH) because different people have different data needs:
Focusing just on new domains may represent an approachable way for new users to get started, sort of like “learning to paddle around the pool” before trying to “swim the English Channel.”
We’ve talked about how some bad guys may attempt to “game the system” by creating a new domain and then letting it “age” for a while before first beginning to use/abuse it. Other bad guys may try other approaches, such as:
Farsight has a solution for those sorts of tactics.
Specifically, imagine a cache of domains that have been seen by a Farsight sensor within the last ten days. If a domain gets seen again by a Farsight sensor during that time, the last-seen-time for that domain in the cache gets updated. If a domain gets does NOT get seen during that ten day window, the domain gets purged from the cache. Domains that subsequently get seen (and which are NOT in the recently-seen cache) are what Farsight tracks in its Newly Active Domains feed, SIE Channel 211.
How does this differ from Farsight’s Newly Observed Domains feed?
Now that you know the difference between Newly Active Domains vs. Newly Observed Domains, you may wonder how the relative volumes compare. At least right now, the answer is:
Clearly many domains “sputter to life” for a bit and then seem to go back to sleep again.
We’ve now talked about newly registered v. newly observed domains, newly observed base domains vs. newly observed fully qualified domain names, and newly observed domains vs. newly active domains.
We have one other “newly ________” product to explain, and that’s “DNS Changes” (aka SIE Channel 214). You can think of Channel 214 as being the “master channel that’s all about what’s new (or newly changed).”
Not surprisingly, the DNS Changes channel is quite busy, typically running about 900 DNS changes/second.
We’re not going to do a deep dive into what a DNS Changes channel record look like here, but know that a new observation gets written to DNS Changes channel whenever:
The other thing you should note about the DNS Changes channel is that there’s a hierarchical relationship to the elements in the “new” element display:
• If new_domain is true, new_rrname, new_rrtype, new_rr, and new_rrset will normally ALSO be true
• If new_rrname is true, new_rrtype, new_rr, and new_rrset will normally ALSO be true
• If new_rrtype is true, new_rr, and new_rrset will normally ALSO be true
• If at least one new_rr is true, new_rrset will normally ALSO be true
We hope the above discussion has helped to clarify the relationship between Newly Observed Domains, Newly Observed Hostnames, Newly Active Hostnames and DNS Changes. We think you’ll be impressed by what they can deliver for you and your company.
Joe St Sauver Ph.D. is a Distinguished Scientist with Farsight Security®, Inc.