{"id":26199,"date":"2026-10-23T18:33:59","date_gmt":"2026-10-23T14:33:59","guid":{"rendered":"https:\/\/me-en.kaspersky.com\/blog\/dga-algorithm-detection-technology\/26199\/"},"modified":"2026-10-23T18:52:36","modified_gmt":"2026-10-23T14:52:36","slug":"dga-algorithm-detection-technology","status":"publish","type":"post","link":"https:\/\/me-en.kaspersky.com\/blog\/dga-algorithm-detection-technology\/26199\/","title":{"rendered":"Technology that blocks spam domains in bulk"},"content":{"rendered":"<p class=\"p1\">We use many technologies to detect email spam. They analyze every part of a message: headers, text, images, and links. But the first thing our email products focus on is the \u201cFrom\u201d field. If the address contains a domain that\u2019s already on our denylist, it\u2019s an easy call. But spammers know the drill, so they register domains in industrial quantities to make emails, even from a single campaign, arrive from completely different addresses. Clearly, they don\u2019t do that by hand. The process has long been automated, and attackers\u2019 algorithms can register huge numbers of domains in a matter of minutes. But every domain needs a name. Coming up with a unique one for each isn\u2019t feasible. So spammers use domain generation algorithms (DGAs), which create similar names with minor variations, based on date and time, pseudo-random numbers, and so on.<\/p>\n<p class=\"p1\">In fact, to block mailings such as these, you don\u2019t need every address on your denylist. We\u2019re good at automating processes, too. For some time now, our email solutions have included a technology that detects domains generated by DGAs, and shuts down entire batch with a single rule. Let me explain how this technology works.<\/p>\n<h2 class=\"p2\">How we detect and block generated domain names in bulk<\/h2>\n<p class=\"p1\">As soon as any of our technologies flags an email as spam, its address becomes subject to further examination. If it meets a number of criteria, its domain is added to our database of domains we consider \u201cbad\u201d. We built a cascade of classifiers that compares these domains by similarity, groups them into clusters, and creates a short but comprehensive rule that blocks the entire cluster. Our email protection solutions receive this rule with an update. From then on, they block all emails sent from addresses on any domain that matches it \u2014 even if those domains have never been used in spam campaigns yet.<\/p>\n<p class=\"p1\">Here\u2019s a real-world example. Let\u2019s say the classifier flags several lookalike domains in a collection of \u201cbad\u201d ones it has gathered:<\/p>\n<ul class=\"ul1\">\n<li class=\"li1\">sxkjcc.asia<\/li>\n<li class=\"li1\">sxkjcd.asia<\/li>\n<li class=\"li1\">sxkjcy.asia<\/li>\n<\/ul>\n<p class=\"p1\">Then, one rule is enough to catch them all: @sxkjc[a-z0-9].asiab<\/p>\n<h2 class=\"p2\">How to protect your company from spam<\/h2>\n<p class=\"p1\">According to <a href=\"https:\/\/securelist.com\/spam-and-phishing-report-2025\/118785\/\" target=\"_blank\" rel=\"noopener\"><span class=\"s1\">our analysis<\/span><\/a>, 44.9% of emails sent last year were spam. Unwanted, unsolicited emails distract employees, waste working time, and clog inboxes. In some cases, they also contain scam, phishing, or malware content. To protect business customers from this deluge of threats, our solutions for <a href=\"https:\/\/www.kaspersky.com\/small-to-medium-business-security\/mail-server?icid=me-en_kdailyplacehold_acq_ona_smm__onl_b2b_kasperskydaily_wpplaceholder____ksms___\" target=\"_blank\" rel=\"noopener nofollow\">corporate email security<\/a> have anti-spam technologies that we constantly improve. This includes the technology described above for blocking domains generated by DGAs.<br>\n<input type=\"hidden\" class=\"category_for_banner\" data-type=\"posts\" value=\"kesb-trial\"><input type=\"hidden\" class=\"placeholder_for_banner\" data-cat_id=\"kesb-trial\" value=\"15341\"><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Spammers automatically register hundreds of near-identical domains to fool security solutions. We can block those domains automatically, too.<\/p>\n","protected":false},"author":2598,"featured_media":26202,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1318,1916,1917],"tags":[1913,19,240,321],"class_list":["post-26199","post","type-post","status-publish","format-standard","has-post-thumbnail","category-business","category-enterprise","category-smb","tag-domains","tag-email","tag-spam","tag-technology"],"hreflang":[{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/dga-algorithm-detection-technology\/26199\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/dga-algorithm-detection-technology\/31168\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/dga-algorithm-detection-technology\/31008\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/dga-algorithm-detection-technology\/42900\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/dga-algorithm-detection-technology\/56597\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/dga-algorithm-detection-technology\/31165\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/dga-algorithm-detection-technology\/36909\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/dga-algorithm-detection-technology\/36581\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/me-en.kaspersky.com\/blog\/tag\/spam\/","name":"spam"},"_links":{"self":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/26199","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/users\/2598"}],"replies":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=26199"}],"version-history":[{"count":1,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/26199\/revisions"}],"predecessor-version":[{"id":26203,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/26199\/revisions\/26203"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/26202"}],"wp:attachment":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=26199"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=26199"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=26199"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}