Abstract: Systems and methods are disclosed for detecting mobile devices. In one implementation, a system includes a web server. The web server receives mobile device detection strings from a DNS server in response to a DNS request and stores the mobile device detection strings on the server. The web server uses the mobile device detection strings to determine if a client device making a request to the web server is a mobile device. The web server may determine if the client device is a mobile device by comparing a user agent string in the request to the mobile device detection strings. The web server may determine whether the client device is a mobile device before sending the client device's request to any server-side scripts stored at the web server.

Abstract: Systems and methods are provided for malware scanning and detection. In one exemplary embodiment, the method includes a hub computing device that receives, from a controller computing device, a scan request, and identifies spoke computing devices for performing the scan request. The method performed by the hub computing device also includes sending to the identified spoke computing devices, the scan request, receiving, from the spoke computing devices, results associated with the scan request, and sending, to the controller computing device, the results associated with the scan request.

Abstract: Disclosed embodiments provide domain name registration, e-mail registration, e-mail forwarding, and other services via resource-limited interfaces, such as SMS-based services. Domain names may be requested, registered, and managed, and e-mail addresses may be requested and forwarding options selected by a user by way of a resource-limited device or protocol. E-mails may be provided to a user over an e-mail-to-SMS forwarding system.

Abstract: A method of triggering crawling of a domain includes receiving information related to a domain from a registrar and processing the information related to the domain. The method also includes storing the processed information in a registry zone file and forming a list of registry data based on the processed information. The list of registry data comprises a subset of the registry zone file. The method further includes crawling one or more of the domains in the list of registry data.

Abstract: Systems and methods for scoring a domain including analyzing counter data and information obtained from a web site associated with the domain. Methods may include receiving requests to resolve the domain at an authoritative domain resolution server. A counter may be incremented for the domain based on the received requests. Information may be obtained from a web page associated with the domain. For example, obtaining information from the web page may include obtaining quantitative, qualitative, and/or functional information from the web page, such as link information, a status of network links corresponding to the link information, and associated ratios. The status of link information may include searching for functional details and/or results, such as, domain redirections, domain errors, mirror content, and commonly linked sites. A score may be calculated for the domain based upon the counter data and the information obtained from the web page associated with the domain.

Abstract: A method for determining probability of a domain name registration renewal includes receiving a plurality of inputs associated with the domain name and assigning each of the plurality of inputs to at least one category from among a plurality of categories. The method also includes assigning a weighted value to each of the plurality of categories and calculating the probability of the domain name registration renewal based in part on the weighted value of each category.

Abstract: Systems and methods for creating and using a domain profile include identifying a status of a first page associated with a domain. The first page is retrieved and additional pages from the domain are identified based on hyperlinks from the first page. The status of the additional pages is identified and the hyperlinks are prioritized based on the status and/or a comparison with predetermined data. Content is extracted from the first page and selected pages from among the additional pages. The specific additional pages may be selected based on the prioritization. The retrieved content may be processed through a signature marker set to determine a contextual match. A purpose of the domain is determined according to the status of the first page, the status of the additional pages and results of the processing of the content. The domain profile can be displayed, stored, sent and/or searched to identify web sites or attributes of interest.

Abstract: An automated method for determining domain traffic including receiving at authoritative name server a request to resolve a domain name that has n labels separated by periods. The leftmost label is the first label and the top level domain is the nth label. If the first label of the received domain name includes the string “www”, then a www hit counter and/or a www requesting server counter for the domain name are incremented. If the received domain name has only two labels, then an exact hit counter and/or an exact requesting server counter for the domain name are incremented. If the first label of the received domain name does not include the string “www” and does not have only two labels, then another hit counter and/or another requesting server counter for the domain name are incremented. A domain traffic score is calculated based upon a plurality of the counters, and calculating the domain traffic score includes applying a weighting factor to at least one of the counters.

Abstract: Systems and methods for scoring a domain web traffic based on DNS traffic requests received at an authoritative name server to resolve the domain name. A request to resolve the domain name is received at an authoritative name server. A counter, such as a server counter or a hit counter, for the domain name is incremented based on the received request. A score, such as a domain traffic score or a domain rank, is calculated based upon a count of the counter. Calculating the score may also include applying a weighting factor to the counters based on information about a requesting set of resolvers and other domains/websites that may be linking and driving traffic to the domain whose traffic score is being calculated. Examples of relevant set of resolvers information may include location, traffic levels, traffic type and architecture of the set of resolvers.