Abstract: The embodiments set forth techniques for facilitating processing checkpoints between computing devices. A method can be performed by at least one first computing device configured to interface with a first server computing device cluster, and include (1) processing objects managed by the first server computing device cluster, where the objects are stored across at least two first partitions associated with the first server computing device cluster, (2) detecting a condition to facilitate a processing checkpoint with at least one second computing device configured to interface with a second server computing device cluster, where the objects are mirrored—but stored differently across at least two second partitions associated with the second server computing device cluster, (3) gathering, from each partition of the at least two first partitions, information associated with a particular number of last-processed objects, and (4) providing the information to the at least one second computing device.

Abstract: The embodiments set forth techniques for facilitating processing checkpoints between computing devices. A method can be performed by at least one first computing device configured to interface with a first server computing device cluster, and include (1) processing objects managed by the first server computing device cluster, where the objects are stored across at least two first partitions associated with the first server computing device cluster, (2) detecting a condition to facilitate a processing checkpoint with at least one second computing device configured to interface with a second server computing device cluster, where the objects are mirrored—but stored differently across at least two second partitions associated with the second server computing device cluster, (3) gathering, from each partition of the at least two first partitions, information associated with a particular number of last-processed objects, and (4) providing the information to the at least one second computing device.

Abstract: The embodiments set forth techniques for facilitating processing checkpoints between computing devices. A method can be performed by at least one first computing device configured to interface with a first server computing device cluster, and include (1) processing objects managed by the first server computing device cluster, where the objects are stored across at least two first partitions associated with the first server computing device cluster, (2) detecting a condition to facilitate a processing checkpoint with at least one second computing device configured to interface with a second server computing device cluster, where the objects are mirrored—but stored differently across at least two second partitions associated with the second server computing device cluster, (3) gathering, from each partition of the at least two first partitions, information associated with a particular number of last-processed objects, and (4) providing the information to the at least one second computing device.

Abstract: The embodiments set forth techniques for facilitating processing checkpoints between computing devices. A method can be performed by at least one first computing device configured to interface with a first server computing device cluster, and include (1) processing objects managed by the first server computing device cluster, where the objects are stored across at least two first partitions associated with the first server computing device cluster, (2) detecting a condition to facilitate a processing checkpoint with at least one second computing device configured to interface with a second server computing device cluster, where the objects are mirrored—but stored differently across at least two second partitions associated with the second server computing device cluster, (3) gathering, from each partition of the at least two first partitions, information associated with a particular number of last-processed objects, and (4) providing the information to the at least one second computing device.

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: 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.

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 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: 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.

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.

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: 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 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: 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.