Domain Name Registry Botnet Watchlist Filtering

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for preventing malicious domain name registrations in the DNS are inefficient and unable to scale with the dynamic nature of botnet operations, failing to continuously monitor and track suspicious domain names, and lack the ability to provide necessary information for law enforcement.

Innovation Solution

Implementing a system where a Registry interacts with a Botnet Management Application to compare requested domain names against a watchlist, setting specific status codes to prevent registration and maintain information for potential botnet domain names, allowing for continuous monitoring and reporting.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If a Registry manually monitors and tracks suspicious domain names, then detection precision improves, but device complexity and loss of time increase

Engineering Contradiction:
Improvedetection precisionVSAvoidsystem complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

A Botnet Management Application is introduced as an intermediary component between the Registry and the domain registration process. This application automatically compares requested domain names against a maintained watchlist of suspicious domains, eliminating the need for complex manual monitoring systems while maintaining high detection precision through automated pattern matching and status code assignment.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The Registry system performs self-service by automatically comparing domain registration requests against the watchlist without requiring external manual intervention. The system autonomously identifies suspicious domains, assigns status codes, and prevents registrations, thereby simplifying the overall system architecture while maintaining high detection capabilities through automated rule-based filtering.

Inventive Principle:
Principle #25Self-service

2Reliability

If a Registry blocks all suspicious domain name registrations, then reliability improves, but loss of information increases

Engineering Contradiction:
ImproveDNS securityVSAvoidregistration information
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The harmful element (suspicious domain registrations) is extracted and isolated from the legitimate domain registration process. By comparing requests against a watchlist and identifying suspicious patterns, the system separates malicious attempts from legitimate registrations, blocking only the harmful ones while preserving all registration information for potential law enforcement analysis.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system converts potentially harmful suspicious domain registration attempts into beneficial security intelligence. By blocking these registrations and maintaining detailed records of the attempts, the system transforms security threats into valuable data for law enforcement, thereby improving DNS security while preserving investigative information.

Inventive Principle:
Principle #22Blessing in disguise (Convert harm into benefit)

3Measurement precision

If a Registry tracks every requested domain name, then measurement precision improves, but productivity decreases

Engineering Contradiction:
Improvemonitoring capabilityVSAvoidregistration processing speed
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

Instead of tracking every single domain name registration request in detail, the system applies partial monitoring by focusing only on requests that match patterns in the watchlist. This selective approach maintains high monitoring precision for suspicious domains while avoiding the productivity loss that would result from comprehensive tracking of all legitimate registrations.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system performs preliminary filtering by comparing domain requests against the watchlist before full processing occurs. This pre-screening approach enables precise monitoring of suspicious domains while maintaining high productivity for legitimate registrations that pass the initial filter, as they proceed through the registration process without additional monitoring overhead.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP2611115B1Method for administering a top-level domain
Publication Date: 2019.10.16 VERISIGN INC
  • EP2611115B1 patent drawingFigure 1
  • EP2611115B1 patent drawingFigure 2
  • EP2611115B1 patent drawingFigure 3

AI summary

A method for administering a top-level domain by analyzing domain name registrations for requests for suspicious or malicious domain names. A request to register a domain name is received (401). The requested domain name's information may be stored in a registry database. The requested domain name may also be conditionally stored in the domain name system (DNS) zone. The requested domain name is compared to a list of botnet domain names stored in a watch list database (403). If the requested domain name corresponds to one of the botnet domain names, the requested domain name is prevented from being added to the DNS zone or is removed from the DNS zone, if it has already been stored there (405). The information regarding the requested domain name is stored in the registry database, even if the domain name does not ultimately stay in the DNS zone (409).