28 Abuse Prevention and Mitigation

Prototypical answer:

gTLDFull Legal NameE-mail suffixDetail
.MAILAfilias Domains No. 2 Limited,afilias.infoView

Afilias will take the requisite operational and technical steps to promote WHOIS data accuracy, limit domain abuse, remove outdated and inaccurate data, and other security measures to ensure the integrity of the TLD. The specific measures include, but are not limited to:
Posting a TLD Anti-Abuse Policy that clearly defines abuse, and provide point-of-contact information for reporting suspected abuse;
Committing to rapid identification and resolution of abuse, including suspensions;
Ensuring completeness of WHOIS information at the time of registration;
Publishing and maintaining procedures for removing orphan glue records for names removed from the zone, and;
Establishing measures to deter WHOIS abuse, including rate-limiting, determining data syntax validity, and implementing and enforcing requirements from the Registry-Registrar Agreement.

Abuse policy

The Anti-Abuse Policy stated below will be enacted under the contractual authority of the registry operator through the Registry-Registrar Agreement, and the obligations will be passed on to and made binding upon registrants. This policy will be posted on the TLD web site along with contact information for registrants or users to report suspected abuse.

The policy is designed to address the malicious use of domain names. The registry operator and its registrars will make reasonable attempts to limit significant harm to Internet users. This policy is not intended to take the place of the Uniform Domain Name Dispute Resolution Policy (UDRP) or the Uniform Rapid Suspension System (URS), and it is not to be used as an alternate form of dispute resolution or as a brand protection mechanism. Its intent is not to burden law-abiding or innocent registrants and domain users; rather, the intent is to deter those who use domain names maliciously by engaging in illegal or fraudulent activity.

Repeat violations of the abuse policy will result in a case-by-case review of the abuser(s), and the registry operator reserves the right to escalate the issue, with the intent of levying sanctions that are allowed under the TLD anti-abuse policy.

The below policy is a recent version of the policy that has been used by the .INFO registry since 2008, and the .ORG registry since 2009. It has proven to be an effective and flexible tool.

.MAIL Anti-Abuse Policy
The following Anti-Abuse Policy is effective upon launch of the TLD. Malicious use of domain names will not be tolerated. The nature of such abuses creates security and stability issues for the registry, registrars, and registrants, as well as for users of the Internet in general. The registry operator definition of abusive use of a domain includes, without limitation, the following:
Illegal or fraudulent actions;
Spam: The use of electronic messaging systems to send unsolicited bulk messages. The term applies to email spam and similar abuses such as instant messaging spam, mobile messaging spam, and the spamming of web sites and Internet forums;
Phishing: The use of counterfeit web pages that are designed to trick recipients into divulging sensitive data such as personally identifying information, usernames, passwords, or financial data;
Pharming: The redirecting of unknowing users to fraudulent sites or services, typically through, but not limited to, DNS hijacking or poisoning;
Willful distribution of malware: The dissemination of software designed to infiltrate or damage a computer system without the ownerʹs informed consent. Examples include, without limitation, computer viruses, worms, keyloggers, and Trojan horses.
Malicious fast-flux hosting: Use of fast-flux techniques with a botnet to disguise the location of web sites or other Internet services, or to avoid detection and mitigation efforts, or to host illegal activities.
Botnet command and control: Services run on a domain name that are used to control a collection of compromised computers or ʺzombies,ʺ or to direct distributed denial-of-service attacks (DDoS attacks);
Illegal Access to Other Computers or Networks: Illegally accessing computers, accounts, or networks belonging to another party, or attempting to penetrate security measures of another individualʹs system (often known as ʺhackingʺ). Also, any activity that might be used as a precursor to an attempted system penetration (e.g., port scan, stealth scan, or other information gathering activity).

Pursuant to the Registry-Registrar Agreement, registry operator reserves the right at its sole discretion to deny, cancel, or transfer any registration or transaction, or place any domain name(s) on registry lock, hold, or similar status, that it deems necessary: (1) to protect the integrity and stability of the registry; (2) to comply with any applicable laws, government rules or requirements, requests of law enforcement, or any dispute resolution process; (3) to avoid any liability, civil or criminal, on the part of registry operator, as well as its affiliates, subsidiaries, officers, directors, and employees; (4) per the terms of the registration agreement and this Anti-Abuse Policy, or (5) to correct mistakes made by registry operator or any registrar in connection with a domain name registration. Registry operator also reserves the right to place upon registry lock, hold, or similar status a domain name during resolution of a dispute.

The policy stated above will be accompanied by notes about how to submit a report to the registry operator’s abuse point of contact, and how to report an orphan glue record suspected of being used in connection with malicious conduct (see below).

Abuse point of contact and procedures for handling abuse complaints

The registry operator will establish an abuse point of contact. This contact will be a role-based e-mail address of the form “abuse@registry.MAIL”. This e-mail address will allow multiple staff members to monitor abuse reports on a 24x7 basis, and then work toward closure of cases as each situation calls for. For tracking purposes, the registry operator will have a ticketing system with which all complaints will be tracked internally. The reporter will be provided with the ticket reference identifier for potential follow-up. Afilias will integrate its existing ticketing system to ensure uniform tracking and handling of the complaint. This role-based approach has been used successfully by ISPs, e-mail service providers, and registrars for many years, and is considered a global best practice.

The registry operator’s designated abuse handlers will then evaluate complaints received via the abuse system address. They will decide whether a particular issue is of concern, and decide what action, if any, is appropriate.

In general, the registry operator will find itself receiving abuse reports from a wide variety of parties, including security researchers and Internet security companies, financial institutions such as banks, Internet users, and law enforcement agencies among others. Some of these parties may provide good forensic data or supporting evidence of the malicious behavior. In other cases, the party reporting an issue may not be familiar with how to provide such data or proof of malicious behavior. It is expected that a percentage of abuse reports to the registry operator will not be actionable, because there will not be enough evidence to support the complaint (even after investigation), and because some reports or reporters will simply not be credible.

The security function includes a communication and outreach function, with information sharing with industry partners regarding malicious or abusive behavior, in order to ensure coordinated abuse mitigation across multiple TLDs.

Assessing abuse reports requires great care, and the registry operator will rely upon professional, trained investigators who are versed in such matters. The goals are accuracy, good record-keeping, and a zero false-positive rate so as not to harm innocent registrants.

Different types of malicious activities require different methods of investigation and documentation. Further, the registry operator expects to face unexpected or complex situations that call for professional advice, and will rely upon professional, trained investigators as needed.

In general, there are two types of domain abuse that must be addressed:
a) Compromised domains. These domains have been hacked or otherwise compromised by criminals, and the registrant is not responsible for the malicious activity taking place on the domain. For example, the majority of domain names that host phishing sites are compromised. The goal in such cases is to get word to the registrant (usually via the registrar) that there is a problem that needs attention with the expectation that the registrant will address the problem in a timely manner. Ideally such domains do not get suspended, since suspension would disrupt legitimate activity on the domain.
b) Malicious registrations. These domains are registered by malefactors for the purpose of abuse. Such domains are generally targets for suspension, since they have no legitimate use.

The standard procedure is that the registry operator will forward a credible alleged case of malicious domain name use to the domain’s sponsoring registrar with a request that the registrar investigate the case and act appropriately. The registrar will be provided evidence collected as a result of the investigation conducted by the trained abuse handlers. As part of the investigation, if inaccurate or false WHOIS registrant information is detected, the registrar is notified about this. The registrar is the party with a direct relationship with—and a direct contract with—the registrant. The registrar will also have vital information that the registry operator will not, such as:
Details about the domain purchase, such as the payment method used (credit card, PayPal, etc.);
The identity of a proxy-protected registrant;
The purchaser’s IP address;
Whether there is a reseller involved, and;
The registrant’s past sales history and purchases in other TLDs (insofar as the registrar can determine this).

Registrars do not share the above information with registry operators due to privacy and liability concerns, among others. Because they have more information with which to continue the investigation, and because they have a direct relationship with the registrant, the registrar is in the best position to evaluate alleged abuse. The registrar can determine if the use violates the registrar’s legal terms of service or the registry Anti-Abuse Policy, and can decide whether or not to take any action. While the language and terms vary, registrars will be expected to include language in their registrar-registrant contracts that indemnifies the registrar if it takes action, and allows the registrar to suspend or cancel a domain name; this will be in addition to the registry Anti-Abuse Policy. Generally, registrars can act if the registrant violates the registrar’s terms of service, or violates ICANN policy, or if illegal activity is involved, or if the use violates the registry’s Anti-Abuse Policy.

If a registrar does not take action within a time period indicated by the registry operator (usually 24 hours), the registry operator might then decide to take action itself. At all times, the registry operator reserves the right to act directly and immediately if the potential harm to Internet users seems significant or imminent, with or without notice to the sponsoring registrar.

The registry operator will be prepared to call upon relevant law enforcement bodies as needed. There are certain cases, for example, Illegal pharmacy domains, where the registry operator will contact the Law Enforcement Agencies to share information about these domains, provide all the evidence collected and work closely with them before any action will be taken for suspension. The specific action is often dependent upon the jurisdiction of which the registry operator, although the operator in all cases will adhere to applicable laws and regulations.

When valid court orders or seizure warrants are received from courts or law enforcement agencies of relevant jurisdiction, the registry operator will order execution in an expedited fashion. Compliance with these will be a top priority and will be completed as soon as possible and within the defined timelines of the order. There are certain cases where Law Enforcement Agencies request information about a domain including but not limited to:
Registration information
History of a domain, including recent updates made
Other domains associated with a registrant’s account
Patterns of registrant portfolio

Requests for such information is handled on a priority basis and sent back to the requestor as soon as possible. Afilias sets a goal to respond to such requests within 24 hours.

The registry operator may also engage in proactive screening of its zone for malicious use of the domains in the TLD, and report problems to the sponsoring registrars. The registry operator could take advantage of a combination of the following resources, among others:
Blocklists of domain names and nameservers published by organizations such as SURBL and Spamhaus.
Anti-phishing feeds, which will provide URLs of compromised and maliciously registered domains being used for phishing.
Analysis of registration or DNS query data [DNS query data received by the TLD nameservers.]

The registry operator will keep records and track metrics regarding abuse and abuse reports. These will include:
Number of abuse reports received by the registry’s abuse point of contact described above;
Number of cases and domains referred to registrars for resolution;
Number of cases and domains where the registry took direct action;
Resolution times;
Number of domains in the TLD that have been blacklisted by major anti-spam blocklist providers, and;
Phishing site uptimes in the TLD.

Removal of orphan glue records

By definition, orphan glue records used to be glue records. Glue records are related to delegations and are necessary to guide iterative resolvers to delegated nameservers. A glue record becomes an orphan when its parent nameserver record is removed without also removing the corresponding glue record. (Please reference the ICANN SSAC paper SAC048 at: http:⁄⁄www.icann.org⁄en⁄committees⁄security⁄sac048.pdf.) Orphan glue records may be created when a domain (example.tld) is placed on EPP ServerHold or ClientHold status. When placed on Hold, the domain is removed from the zone and will stop resolving. However, any child nameservers (now orphan glue) of that domain (e.g., ns1.example.tld) are left in the zone. It is important to keep these orphan glue records in the zone so that any innocent sites using that nameserver will continue to resolve. This use of Hold status is an essential tool for suspending malicious domains.

Afilias observes the following procedures, which are being followed by other registries and are generally accepted as DNS best practices. These procedures are also in keeping with ICANN SSAC recommendations.

When a request to delete a domain is received from a registrar, the registry first checks for the existence of glue records. If glue records exist, the registry will check to see if other domains in the registry are using the glue records. If other domains in the registry are using the glue records then the request to delete the domain will fail until no other domains are using the glue records. If no other domains in the registry are using the glue records then the glue records will be removed before the request to delete the domain is satisfied. If no glue records exist then the request to delete the domain will be satisfied.

If a registrar cannot delete a domain because of the existence of glue records that are being used by other domains, then the registrar may refer to the zone file or the “weekly domain hosted by nameserver report” to find out which domains are using the nameserver in question and attempt to contact the corresponding registrar to request that they stop using the nameserver in the glue record. The registry operator does not plan on performing mass updates of the associated DNS records.

The registry operator will accept, evaluate, and respond appropriately to complaints that orphan glue is being used maliciously. Such reports should be made in writing to the registry operator, and may be submitted to the registry’s abuse point-of-contact. If it is confirmed that an orphan glue record is being used in connection with malicious conduct, the registry operator will have the orphan glue record removed from the zone file. Afilias has the technical ability to execute such requests as needed.

Methods to promote WHOIS accuracy

The creation and maintenance of accurate WHOIS records is an important part of registry management. As described in our response to question #26, WHOIS, the registry operator will manage a secure, robust and searchable WHOIS service for this TLD.

WHOIS data accuracy
The registry operator will offer a “thick” registry system. In this model, all key contact details for each domain name will be stored in a central location by the registry. This allows better access to domain data, and provides uniformity in storing the information. The registry operator will ensure that the required fields for WHOIS data (as per the defined policies for the TLD) are enforced at the registry level. This ensures that the registrars are providing required domain registration data. Fields defined by the registry policy to be mandatory are documented as such and must be submitted by registrars. The Afilias registry system verifies formats for relevant individual data fields (e.g. e-mail, and phone⁄fax numbers). Only valid country codes are allowed as defined by the ISO 3166 code list. The Afilias WHOIS system is extensible, and is capable of using the VAULT system, described further below.

Similar to the centralized abuse point of contact described above, the registry operator can institute a contact email address which could be utilized by third parties to submit complaints for inaccurate or false WHOIS data detected. This information will be processed by Afilias’ support department and forwarded to the registrars. The registrars can work with the registrants of those domains to address these complaints. Afilias will audit registrars on a yearly basis to verify whether the complaints being forwarded are being addressed or not. This functionality, available to all registry operators, is activated based on the registry operator’s business policy.

Afilias also incorporates a spot-check verification system where a randomly selected set of domain names are checked periodically for accuracy of WHOIS data. Afilias’ .PRO registry system incorporates such a verification system whereby 1% of total registrations or 100 domains, whichever number is larger, are spot-checked every month to verify the domain name registrant’s critical information provided with the domain registration data. With both a highly qualified corps of engineers and a 24x7 staffed support function, Afilias has the capacity to integrate such spot-check functionality into this TLD, based on the registry operator’s business policy. Note: This functionality will not work for proxy protected WHOIS information, where registrars or their resellers have the actual registrant data. The solution to that problem lies with either registry or registrar policy, or a change in the general marketplace practices with respect to proxy registrations.

Finally, Afilias’ registry systems have a sophisticated set of billing and pricing functionality which aids registry operators who decide to provide a set of financial incentives to registrars for maintaining or improving WHOIS accuracy. For instance, it is conceivable that the registry operator may decide to provide a discount for the domain registration or renewal fees for validated registrants, or levy a larger cost for the domain registration or renewal of proxy domain names. The Afilias system has the capability to support such incentives on a configurable basis, towards the goal of promoting better WHOIS accuracy.

Role of registrars
As part of the RRA (Registry Registrar Agreement), the registry operator will require the registrar to be responsible for ensuring the input of accurate WHOIS data by their registrants. The Registrar⁄Registered Name Holder Agreement will include a specific clause to ensure accuracy of WHOIS data, and to give the registrar rights to cancel or suspend registrations if the Registered Name Holder fails to respond to the registrar’s query regarding accuracy of data. ICANN’s WHOIS Data Problem Reporting System (WDPRS) will be available to those who wish to file WHOIS inaccuracy reports, as per ICANN policy (http:⁄⁄wdprs.internic.net⁄).

Controls to ensure proper access to domain functions

Several measures are in place in the Afilias registry system to ensure proper access to domain functions, including authentication provisions in the RRA relative to notification and contact updates via use of AUTH-INFO codes.

IP address access control lists, TLS⁄SSL certificates and proper authentication are used to control access to the registry system. Registrars are only given access to perform operations on the objects they sponsor.

Every domain will have a unique AUTH-INFO code. The AUTH-INFO code is a 6- to 16-character code assigned by the registrar at the time the name is created. Its purpose is to aid identification of the domain owner so proper authority can be established. It is the ʺpasswordʺ to the domain name. Registrars must use the domain’s password in order to initiate a registrar-to-registrar transfer. It is used to ensure that domain updates (update contact information, transfer, or deletion) are undertaken by the proper registrant, and that this registrant is adequately notified of domain update activity. Only the sponsoring registrar of a domain has access to the domain’s AUTH-INFO code stored in the registry, and this is accessible only via encrypted, password-protected channels.

Information about other registry security measures such as encryption and security of registrar channels are confidential to ensure the security of the registry system. The details can be found in the response to question #30b.

Validation and abuse mitigation mechanisms

Afilias has developed advanced validation and abuse mitigation mechanisms. These capabilities and mechanisms are described below. These services and capabilities are discretionary and may be utilized by the registry operator based on their policy and business need.

Afilias has the ability to analyze the registration data for known patterns at the time of registration. A database of these known patterns is developed from domains and other associated objects (e.g., contact information) which have been previously detected and suspended after being flagged as abusive. Any domains matching the defined criteria can be flagged for investigation. Once analyzed and confirmed by the domain anti-abuse team members, these domains may be suspended. This provides proactive detection of abusive domains.

Provisions are available to enable the registry operator to only allow registrations by pre-authorized and verified contacts. These verified contacts are given a unique code that can be used for registration of new domains.

Registrant pre-verification and authentication

One of the systems that could be used for validity and identity authentication is VAULT (Validation and Authentication Universal Lookup). It utilizes information obtained from a series of trusted data sources with access to billions of records containing data about individuals for the purpose of providing independent age and id verification as well as the ability to incorporate additional public or private data sources as required. At present it has the following: US Residential Coverage - 90% of Adult Population and also International Coverage - Varies from Country to Country with a minimum of 80% coverage (24 countries, mostly European).

Various verification elements can be used. Examples might include applicant data such as name, address, phone, etc. Multiple methods could be used for verification include integrated solutions utilizing API (XML Application Programming Interface) or sending batches of requests.

Verification and Authentication requirements would be based on TLD operator requirements or specific criteria.
Based on required WHOIS Data; registrant contact details (name, address, phone)
If address⁄ZIP can be validated by VAULT, the validation process can continue (North America +25 International countries)
If in-line processing and registration and EPP⁄API call would go to the verification clearinghouse and return up to 4 challenge questions.
If two-step registration is required, then registrants would get a link to complete the verification at a separate time. The link could be specific to a domain registration and pre-populated with data about the registrant.
If WHOIS data is validated a token would be generated and could be given back to the registrar which registered the domain.
WHOIS data would reflect the Validated Data or some subset, i.e., fields displayed could be first initial and last name, country of registrant and date validated. Other fields could be generic validation fields much like a “privacy service”.
A “Validation Icon” customized script would be sent to the registrants email address. This could be displayed on the website and would be dynamically generated to avoid unauthorized use of the Icon. When clicked on the Icon would should limited WHOIS details i.e. Registrant: jdoe, Country: USA, Date Validated: March 29, 2011, as well as legal disclaimers.
Validation would be annually renewed, and validation date displayed in the WHOIS.

Abuse prevention resourcing plans

Since its founding, Afilias is focused on delivering secure, stable and reliable registry services. Several essential management and staff who designed and launched the Afilias registry in 2001 and expanded the number of TLDs supported, all while maintaining strict service levels over the past decade, are still in place today. This experiential continuity will endure for the implementation and on-going maintenance of this TLD. Afilias operates in a matrix structure, which allows its staff to be allocated to various critical functions in both a dedicated and a shared manner. With a team of specialists and generalists, the Afilias project management methodology allows efficient and effective use of our staff in a focused way. Abuse prevention and detection is a function that is staffed across the various groups inside Afilias, and requires a team effort when abuse is either well hidden or widespread, or both. While all of Afilias’ 200+ employees are charged with responsibility to report any detected abuse, the engineering and analysis teams, numbering over 30, provide specific support based on the type of abuse and volume and frequency of analysis required. The Afilias security and support teams have the authority to initiate mitigation.

Afilias has developed advanced validation and abuse mitigation mechanisms. These capabilities and mechanisms are described below. These services and capabilities are discretionary and may be utilized by the registry operator based on their policy and business need.

This TLD’s anticipated volume of registrations in the first three years of operations is listed in response #46. Afilias’ anti-abuse function anticipates the expected volume and type of registrations, and together will adequately cover the staffing needs for this TLD. The registry operator will maintain an abuse response team, which may be a combination of internal staff and outside specialty contractors, adjusting to the needs of the size and type of TLD. The team structure planned for this TLD is based on several years of experience responding to, mitigating, and managing abuse for TLDs of various sizes. The team will generally consist of abuse handlers (probably internal), a junior analyst, (either internal or external), and a senior security consultant (likely an external resource providing the registry operator with extra expertise as needed). These responders will be specially trained in the investigation of abuse complaints, and will have the latitude to act expeditiously to suspend domain names (or apply other remedies) when called for.

The exact resources required to maintain an abuse response team must change with the size and registration procedures of the TLD. An initial abuse handler is necessary as a point of contact for reports, even if a part-time responsibility. The abuse handlers monitor the abuse email address for complaints and evaluate incoming reports from a variety of sources. A large percentage of abuse reports to the registry operator may be unsolicited commercial email. The designated abuse handlers can identify legitimate reports and then decide what action is appropriate, either to act upon them, escalate to a security analyst for closer investigation, or refer them to registrars as per the above-described procedures. A TLD with rare cases of abuse would conform to this structure.

If multiple cases of abuse within the same week occur regularly, the registry operator will consider staffing internally an additional security analyst to investigate the complaints as they become more frequent. Training an abuse analyst requires 3-6 months and likely requires the active guidance of an experienced senior security analyst for guidance and verification of assessments and recommendations being made.

If this TLD were to regularly experience multiple cases of abuse within the same day, a full-time senior security analyst would likely be necessary. A senior security analyst capable of fulfilling this role should have several years of experience and able to manage and train the internal abuse response team.

The abuse response team will also maintain subscriptions for several security information services, including the blocklists from organizations like SURBL and Spamhaus and anti-phishing and other domain related abuse (malware, fast-flux etc.) feeds. The pricing structure of these services may depend on the size of the domain and some services will include a number of rapid suspension requests for use as needed.

For a large TLD, regular audits of the registry data are required to maintain control over abusive registrations. When a registrar with a significant number of registrations has been compromised or acted maliciously, the registry operator may need to analyze a set of registration or DNS query data. A scan of all the domains of a registrar is conducted only as needed. Scanning and analysis for a large registrar may require as much as a week of full-time effort for a dedicated machine and team.

Similar gTLD applications: (325)

gTLDFull Legal NameE-mail suffixzDetail
.WEBAfilias Domains No. 3 Limited,afilias.info-4.7Compare
.MLSAfilias Limitedafilias.info-4.7Compare
.MEMORIALAfilias Limitedafilias.info-4.7Compare
.RADIOAfilias Limitedafilias.info-4.7Compare
.POKERAfilias Domains No. 5 Limitedafilias.info-4.7Compare
.TEAMAfilias Limitedafilias.info-4.7Compare
.DESIAfilias Domains No. 4 Limited,afilias.info-4.7Compare
.MEETAfilias Limitedafilias.info-4.7Compare
.BLUEAfilias Limitedafilias.info-4.7Compare
.REDAfilias Limitedafilias.info-4.7Compare
.PETAfilias Limitedafilias.info-4.7Compare
.WINEAfilias Limitedafilias.info-4.7Compare
.PINKAfilias Limitedafilias.info-4.7Compare
.KIMAfilias Limitedafilias.info-4.7Compare
.ORGANICAfilias Limitedafilias.info-4.7Compare
.BLACKAfilias Limitedafilias.info-4.7Compare
.SHIKSHAAfilias Limitedafilias.info-4.7Compare
.APPAfilias Limitedafilias.info-4.7Compare
.BLOGAfilias Domains No. 1 Limitedafilias.info-4.7Compare
.greenAfilias Limitedafilias.info-4.7Compare
.INCAfilias Limitedafilias.info-4.7Compare
.LTDAfilias Limitedafilias.info-4.7Compare
.LOTTOAfilias Limitedafilias.info-4.69Compare
.CASINOAfilias Limitedafilias.info-4.69Compare
.BETAfilias Limitedafilias.info-4.69Compare
.LGBTAfilias Limitedafilias.info-4.69Compare
.HEALTHAfilias Limitedafilias.info-4.69Compare
.llcAfilias Limitedafilias.info-4.69Compare
.信息Afilias Limitedafilias.info-4.69Compare
.移动Afilias Limitedafilias.info-4.68Compare
.dataDish DBS Corporationcscinfo.com-4.68Compare
.latinoDish DBS Corporationcscinfo.com-4.68Compare
.directDish DBS Corporationcscinfo.com-4.68Compare
.blockbusterDish DBS Corporationcscinfo.com-4.68Compare
.movieDish DBS Corporationcscinfo.com-4.68Compare
.goodyearThe Goodyear Tire & Rubber Companycscinfo.com-4.68Compare
.dunlopThe Goodyear Tire & Rubber Companycscinfo.com-4.68Compare
.tiresThe Goodyear Tire & Rubber Companycscinfo.com-4.68Compare
.moparChrysler Group LLC.cscinfo.com-4.68Compare
.srtChrysler Group LLC.cscinfo.com-4.68Compare
.chryslerChrysler Group LLC.cscinfo.com-4.68Compare
.ramChrysler Group LLC.cscinfo.com-4.68Compare
.beknownMonster Worldwide, Inc.cscinfo.com-4.68Compare
.cebThe Corporate Executive Board Companycscinfo.com-4.68Compare
.monsterMonster Worldwide, Inc.cscinfo.com-4.68Compare
.vikingViking River Cruises (Bermuda) Ltd.cscinfo.com-4.68Compare
.cruiseViking River Cruises (Bermuda) Ltd.cscinfo.com-4.68Compare
.insuranceProgressive Casualty Insurance Companycscinfo.com-4.68Compare
.progressiveProgressive Casualty Insurance Companycscinfo.com-4.68Compare
.lasalleJones Lang LaSalle Incorporatedcscinfo.com-4.68Compare
.gallupGallup, Inc.cscinfo.com-4.68Compare
.ciprianiHotel Cipriani Srlcscinfo.com-4.68Compare
.orientexpressOrient-Express Hotels Ltd.cscinfo.com-4.68Compare
.naturaNATURA COSMÉTICOS S.A.cscinfo.com-4.68Compare
.pncPNC Domain Co., LLCcscinfo.com-4.68Compare
.uconnectChrysler Group LLC.cscinfo.com-4.68Compare
.jeepChrysler Group LLC.cscinfo.com-4.68Compare
.jllJones Lang LaSalle Incorporatedcscinfo.com-4.68Compare
.工行Industrial and Commercial Bank of China Limitedhichina.com-4.68Compare
.BLOGBET Inc.afilias.info-4.68Compare
.vipI-REGISTRY Ltd., Niederlassung Deutschlandi-registry.com-4.68Compare
.newhollandFiat Industrial S.p.A (società per azioni)cscinfo.com-4.68Compare
.lockerDish DBS Corporationcscinfo.com-4.68Compare
.mzansimagicElectronic Media Network Limited (M-Net)cscinfo.com-4.68Compare
.upsUPS Market Driver, Inc.cscinfo.com-4.68Compare
.gmcGeneral Motors LLCcscinfo.com-4.68Compare
.africamagicElectronic Media Network Limited (M-Net)cscinfo.com-4.68Compare
.supersportSuperSport International Holdings Limitedcscinfo.com-4.68Compare
.mnetElectronic Media Network Limited (M-Net)cscinfo.com-4.68Compare
.multichoiceMultiChoice Africa (Proprietary) Limitedcscinfo.com-4.68Compare
.caseihFiat Industrial S.p.A (società per azioni)cscinfo.com-4.68Compare
.payuMIH PayU B.V.cscinfo.com-4.68Compare
.mihMyriad International Holdings B.V.cscinfo.com-4.68Compare
.naspersIntelprop (Proprietary) Limitedcscinfo.com-4.68Compare
.shopyourwayShop Your Way, Inc.cscinfo.com-4.68Compare
.GECOMPANYGE GTLD Holdings LLCreedsmith.com-4.68Compare
.caseFiat Industrial S.p.A (società per azioni)cscinfo.com-4.68Compare
.emersonEmerson Electric Co.cscinfo.com-4.68Compare
.mobileDish DBS Corporationcscinfo.com-4.68Compare
.digikeyDigi-Key Corporationdigikey.com-4.68Compare
.phoneDish DBS Corporationcscinfo.com-4.68Compare
.olloDish DBS Corporationcscinfo.com-4.68Compare
.dvrHughes Satellite Systems Corporationcscinfo.com-4.68Compare
.hughesHughes Satellite Systems Corporationcscinfo.com-4.68Compare
.cadillacGeneral Motors LLCcscinfo.com-4.68Compare
.dotDish DBS Corporationcscinfo.com-4.68Compare
.chevroletGeneral Motors LLCcscinfo.com-4.68Compare
.ivecoFiat Industrial S.p.A (società per azioni)cscinfo.com-4.68Compare
.streamHughes Satellite Systems Corporationcscinfo.com-4.68Compare
.abarthFiat S.p.A. (ʺsocietà per azioniʺ)cscinfo.com-4.68Compare
.chevyGeneral Motors LLCcscinfo.com-4.68Compare
.bcgThe Boston Consulting Group, Inc.cscinfo.com-4.68Compare
.slingHughes Satellite Systems Corporationcscinfo.com-4.68Compare
.buickGeneral Motors LLCcscinfo.com-4.68Compare
.boehringerBoehringer Ingelheim Pharma GmbH & Co. KGcscinfo.com-4.68Compare
.alfaromeoFiat S.p.A. (ʺsocietà per azioniʺ)cscinfo.com-4.68Compare
.lanciaFiat S.p.A. (ʺsocietà per azioniʺ)cscinfo.com-4.68Compare
.maseratiFiat S.p.A. (ʺsocietà per azioniʺ)cscinfo.com-4.68Compare
.lamerELC Online Inc.cscinfo.com-4.68Compare
.fiatFiat S.p.A. (ʺsocietà per azioniʺ)cscinfo.com-4.68Compare
.cliniqueELC Online Inc.cscinfo.com-4.68Compare
.dishDish DBS Corporationcscinfo.com-4.68Compare
.kyknetElectronic Media Network Limited (M-Net)cscinfo.com-4.68Compare
.gotvMultiChoice Africa (Proprietary) Limitedcscinfo.com-4.68Compare
.originsELC Online Inc.cscinfo.com-4.68Compare
.jcpJCP Media, Inc.cscinfo.com-4.68Compare
.dodgeChrysler Group LLC.cscinfo.com-4.68Compare
.fedexFederal Express Corporationcscinfo.com-4.68Compare
.DESIGNBET Inc.afilias.info-4.68Compare
.onlineI-REGISTRY Ltd., Niederlassung Deutschlandi-registry.com-4.68Compare
.dtvDish DBS Corporationpattonboggs.com-4.68Compare
.richI-REGISTRY Ltd., Niederlassung Deutschlandi-registry.com-4.68Compare
.alipayAlibaba Group Holding Limitedhichina.com-4.68Compare
.onlI-REGISTRY Ltd., Niederlassung Deutschlandi-registry.com-4.68Compare
.alibabaAlibaba Group Holding Limitedhichina.com-4.68Compare
.ICBCIndustrial and Commercial Bank of China Limitedhichina.com-4.68Compare
.CyouBeijing Gamease Age Digital Technology Co., Ltd.hichina.com-4.68Compare
.RedstoneRedstone Haute Couture Co., Ltd.hichina.com-4.68Compare
.aigoaigo Digital Technology Co,Ltd.hichina.com-4.68Compare
.scholarshipsScholarships.com, LLCscholarships.com-4.68Compare
.pwcPwC Business Trustcscinfo.com-4.68Compare
.transunionTrans Union LLCcscinfo.com-4.68Compare
.bbbCouncil of Better Business Bureaus, Inc.cscinfo.com-4.68Compare
.allyAlly Financial Inc.cscinfo.com-4.68Compare
.APP.APP REGISTRY INC.afilias.info-4.67Compare
.helsinkiCity of Helsinkihel.fi-4.67Compare
.nraNRA Holdings Company, INC.afilias.info-4.67Compare
.vegasDot Vegas, Inc.mackayventures.com-4.67Compare
.TICKETSTickets TLD LLCafilias.info-4.67Compare
.ferrariFiat S.p.A. (ʺsocietà per azioniʺ)cscinfo.com-4.67Compare
.dstvMultiChoice Africa (Proprietary) Limitedcscinfo.com-4.67Compare
.mckinseyMcKinsey Holdings, Inc.cscinfo.com-4.67Compare
.metlifeMetLife Services and Solutions, LLCcscinfo.com-4.67Compare
.chatrRogers Communications Partnershiprci.rogers.com-4.67Compare
.rogersRogers Communications Partnershiprci.rogers.com-4.67Compare
.fidoRogers Communications Partnershiprci.rogers.com-4.67Compare
.NOWGlobal Top Level ApSglobaltoplevel.com-4.67Compare
.GAMEBeijing Gamease Age Digital Technology Co., Ltd.hichina.com-4.67Compare
.fageFAGE Dairy Industry S.A.winston.com-4.67Compare
.xinElegant Leader Limitedhichina.com-4.67Compare
.ottDish DBS Corporationcscinfo.com-4.67Compare
.LLCmyLLC GmbHafilias.info-4.67Compare
.travelersinsuranceTravelers TLD, LLCcscinfo.com-4.67Compare
.LLPmyLLP GmbHafilias.info-4.67Compare
.LTDmyLTD GmbHafilias.info-4.67Compare
.SARLmySARL GmbHafilias.info-4.67Compare
.volkswagenVolkswagen Group of America Inc.indeca.de-4.67Compare
.relianceReliance Industries Limitedril.com-4.67Compare
.MORMONIRI Domain Management, LLC (ʺApplicantʺ)kmclaw.com-4.67Compare
.schaefflerSchaeffler Technologies AG & Co. KGlemarit.com-4.67Compare
.HOME.HOME REGISTRY INC.afilias.info-4.67Compare
.sbiSTATE BANK OF INDIAsbi.co.in-4.67Compare
.stockholmStockholms kommundipcon.com-4.67Compare
.shriramShriram Capital Ltd.shriram.com-4.67Compare
.indiansReliance Industries Limitedril.com-4.67Compare
.rilReliance Industries Limitedril.com-4.67Compare
.hdfcbankHDFC Bank Limitedhdfcbank.com-4.67Compare
.SRLmySRL GmbHafilias.info-4.67Compare
.VOTOMonolith Registry LLCafilias.info-4.67Compare
.VOTEMonolith Registry LLCafilias.info-4.67Compare
.airtelBharti Airtel Limitedbharti.in-4.67Compare
.corpDOTCORP LIMITEDcorpregistry.net-4.67Compare
.KOSHERKosher Marketing Assets LLCafilias.info-4.67Compare
.daburDabur India Limiteddabur.com-4.67Compare
.statebankSTATE BANK OF INDIAsbi.co.in-4.67Compare
.hairYour Hair Limitedafilias.info-4.67Compare
.WEBSchlund Technologies GmbHafilias.info-4.67Compare
.tataTATA SONS LIMITEDtata.com-4.67Compare
.hotelHOTEL Top-Level-Domain S.a.r.ldothotel.info-4.67Compare
.trvTravelers TLD, LLCcscinfo.com-4.67Compare
.jioAffinity Names, Inc.afilias.info-4.67Compare
.通用电气公司GE GTLD Holdings LLCreedsmith.com-4.67Compare
.northlandinsuranceTravelers TLD, LLCcscinfo.com-4.67Compare
.YunQIHOO 360 TECHNOLOGY CO. LTD.360.cn-4.67Compare
.ShoujiQIHOO 360 TECHNOLOGY CO. LTD.360.cn-4.67Compare
.XihuanQIHOO 360 TECHNOLOGY CO. LTD.360.cn-4.67Compare
.AnquanQIHOO 360 TECHNOLOGY CO. LTD.360.cn-4.67Compare
.SinaSina Corporationstaff.weibo.com-4.67Compare
.WeiboSina Corporationstaff.weibo.com-4.67Compare
.微博Sina Corporationstaff.weibo.com-4.67Compare
.istIstanbul Metropolitan Municipalitygmail.com-4.66Compare
.travelersTravelers TLD, LLCcscinfo.com-4.66Compare
.EXTRASPACEExtra Space Storage LLCmsn.com-4.66Compare
.BaiduBaidu, Inc.baidu.com-4.66Compare
.bhartiBharti Enterprises (Holding) Private Limitedbharti.in-4.66Compare
.bookR.R. Bowker LLCbowker.com-4.66Compare
.istanbulIstanbul Metropolitan Municipalitygmail.com-4.66Compare
.appleApple Inc.cscinfo.com-4.66Compare
.activeThe Active Network, Incactivenetwork.com-4.66Compare
.手机Beijing RITT-Net Technology Development Co., Ltdafilias.info-4.66Compare
.bugattiBugatti International SAindeca.de-4.66Compare
.geaGEA Group Aktiengesellschaftgeagroup.com-4.66Compare
.موقعSuhub Electronic Establishmentafilias.info-4.66Compare
.audiAUDI Aktiengesellschaftindeca.de-4.66Compare
.stadaSTADA Arzneimittel AGopportunity.de-4.65Compare
.acoACO Severin Ahlmann GmbH & Co. KGaco.com-4.65Compare
.redumbrellaTravelers TLD, LLCcscinfo.com-4.65Compare
.大众汽车Volkswagen (China) Investment Co., Ltd.indeca.de-4.65Compare
.promoPhenomena Group Oyphenomena.com-4.65Compare
.edekaEDEKA Verband kaufmännischer Genossenschaften e.V.dotzon.com-4.64Compare
.lamborghiniAutomobili Lamborghini S.p.A.indeca.de-4.64Compare
.ART.ART REGISTRY INC.afilias.info-4.64Compare
.GolfDot-Golf LLCtldassets.com-4.63Compare
.SaleDot-Sale LLCsaledomain.name-4.63Compare
.IrishDot-Irish LLCtldassets.com-4.63Compare
.globalCloudNames AScloudnames.com-4.61Compare
.cloudCloudNames AScloudnames.com-4.61Compare
.ticketsAccent Media Limitedcloudnames.com-4.6Compare
.VIGVIENNA INSURANCE GROUP AG Wiener Versicherung Gruppesedari.com-4.59Compare
.GCCGCCIX WLLsedari.com-4.59Compare
.CITYTLD REGISTRY LIMITEDsedari.com-4.59Compare
.CHKAfterdot LLCsedari.com-4.59Compare
.在线TLD REGISTRY LIMITEDsedari.com-4.59Compare
.中文网TLD REGISTRY LIMITEDsedari.com-4.59Compare
.DELTADelta Air Lines, Inc.sedari.com-4.59Compare
.CHESAPEAKEAfterdot LLCsedari.com-4.59Compare
.delmonteDel Monte International GmbHfreshdelmonte.com-4.58Compare
.SHAWShaw Cablesystems G.P.afilias.info-4.58Compare
.starStar India Private Limitedgmail.com-4.57Compare
.nowStarbucks (HK) Limitedtld.asia-4.56Compare
.kidsDotKids Foundation Limitedtld.asia-4.56Compare
.nokiaNokia Corporationvalideus.com-4.55Compare
.诺基亚Nokia Corporationvalideus.com-4.55Compare
.IMAMATFondation Aga Khan (Aga Khan Foundation)afilias.info-4.55Compare
.AKDNFondation Aga Khan (Aga Khan Foundation)afilias.info-4.55Compare
.ISMAILIFondation Aga Khan (Aga Khan Foundation)afilias.info-4.55Compare
.AGAKHANFondation Aga Khan (Aga Khan Foundation)afilias.info-4.55Compare
.homedepotHomer TLC, Inc.cscinfo.com-4.55Compare
.thdHomer TLC, Inc.cscinfo.com-4.55Compare
.AVIANCAAerovias del Continente Americano S.A. Aviancaafilias.info-4.52Compare
.LDSIRI Domain Management, LLC (ʺApplicantʺ)kmclaw.com-4.51Compare
.GEDGED Domains LLCgedtestingservice.com-4.48Compare
.淡马锡Temasek Holdings (Private) Limtiedtemasek.com.sg-4.47Compare
.temasekTemasek Holdings (Private) Limtiedtemasek.com.sg-4.47Compare
.CIMBCIMB Group Sdn Bhdipmirror.com-4.47Compare
.BNLBanca Nazionale del Lavorobnlmail.com-4.46Compare
.BNPPARIBASBNP Paribasbnpparibas.com-4.46Compare
.hivdotHIV gemeinnuetziger e.V.dothiv.org-4.44Compare
.ITVITV Services Limitedvalideus.com-4.33Compare
.HOMEDotHome ⁄ CGR E-Commerce Ltddothome.net-4.32Compare
.机构Public Interest Registrypir.org-4.32Compare
.机构体制Public Interest Registrypir.org-4.32Compare
.संगठनPublic Interest Registrypir.org-4.32Compare
.оргPublic Interest Registrypir.org-4.32Compare
.nowtvStarbucks (HK) Limitedtld.asia-4.31Compare
.richardliPacific Century Asset Management (HK) Limitedtld.asia-4.31Compare
.香港電訊PCCW-HKT DataCom Services Limitedtld.asia-4.31Compare
.電訊盈科PCCW Enterprises Limitedtld.asia-4.31Compare
.hktPCCW-HKT DataCom Services Limitedtld.asia-4.31Compare
.pccwPCCW Enterprises Limitedtld.asia-4.31Compare
.strokeAmerican Heart Association, Inc.heart.org-4.3Compare
.cernEuropean Organization for Nuclear Research (ʺCERNʺ)cern.ch-4.26Compare
.sewSEW-EURODRIVE GmbH & Co KGsew-eurodrive.de-4.26Compare
.CBSCBS Domains Inc.fairwindspartners.com-4.24Compare
.wolterskluwerWolters Kluwer N.V.valideus.com-4.23Compare
.SHOWTIMECBS Domains Inc.fairwindspartners.com-4.22Compare
.heartAmerican Heart Association, Inc.heart.org-4.22Compare
.SECURITYDefender Security Companydefenderdirect.com-4.2Compare
.MUSICDotMusic ⁄ CGR E-Commerce Ltdmusic.us-4.18Compare
.ABBVIEAbbott Laboratoriesfairwindspartners.com-4.17Compare
.ABBOTTAbbott Laboratoriesfairwindspartners.com-4.17Compare
.CARSDERCars, LLCdominionenterprises.com-4.16Compare
.HOMESDERHomes, LLCdominionenterprises.com-4.16Compare
.RENTDERRent, LLCdominionenterprises.com-4.16Compare
.APARTMENTSDERApartments, LLCdominionenterprises.com-4.16Compare
.BOATSDERBoats, LLCdominionenterprises.com-4.16Compare
.MOTORCYCLESDERMotorcycles, LLCdominionenterprises.com-4.16Compare
.YACHTSDERYachts, LLCdominionenterprises.com-4.16Compare
.FORSALEDERForsale, LLCdominionenterprises.com-4.16Compare
.AUTOSDERAutos, LLCdominionenterprises.com-4.16Compare
.mitMassachusetts Institute of Technologymit.edu-4.13Compare
.wilmarWilmar International Limitedwilmar.com.sg-4.11Compare
.BUYAmazon EU S.à r.l.valideus.com-4.07Compare
.BESTBUYBBY Solutions, Inc.fairwindspartners.com-4.07Compare
.SHOPAmazon EU S.à r.l.valideus.com-4.07Compare
.PLAYAmazon EU S.à r.l.valideus.com-4.07Compare
.GIFTSLucy Ventures, LLCfairwindspartners.com-4.04Compare
.FLOWERSPiper Ventures, LLCfairwindspartners.com-4.02Compare
.ZARAIndustria de Diseño Textil, S.A. (INDITEX, S.A.)valideus.com-4.01Compare
.ECOBig Room Inc.doteco.org-3.97Compare
.creditunionCUNA Performance Resources, LLCcuna.com-3.95Compare
.ESURANCEEsurance Insurance Companyfairwindspartners.com-3.94Compare
.MARRIOTTMarriott Worldwide Corporationfairwindspartners.com-3.93Compare
.storageSelf Storage Company LLCextraspace.com-3.86Compare
.pornICM Registry PN LLCicmregistry.com-3.85Compare
.sexICM Registry SX LLCicmregistry.com-3.85Compare
.adultICM Registry AD LLClawley.com-3.85Compare
.CARINSURANCEAllstate Fire and Casualty Insurance Companyfairwindspartners.com-3.68Compare
.AUTOINSURANCEAllstate Fire and Casualty Insurance Companyfairwindspartners.com-3.68Compare
.GOODHANDSAllstate Fire and Casualty Insurance Companyfairwindspartners.com-3.67Compare
.ALLSTATEAllstate Fire and Casualty Insurance Companyfairwindspartners.com-3.67Compare
.emerckMerck KGaAbettinger.de-3.54Compare
.taxStorm Orchard, LLCdonuts.co-3.23Compare
.insuranceAuburn Park, LLCdonuts.co-3.23Compare
.healthGoose Fest, LLCdonuts.co-3.23Compare
.financeCotton Cypress, LLCdonuts.co-3.23Compare
.claimsBlack Corner, LLCdonuts.co-3.23Compare
.musicVictor Crossdonuts.co-3.23Compare
.surgeryTin Avenue, LLCdonuts.co-3.23Compare
.medicalSteel Hill, LLCdonuts.co-3.23Compare
.loansJune Woods, LLCdonuts.co-3.23Compare
.lawyerAtomic Station, LLCdonuts.co-3.23Compare
.juegosGoose Gardens, LLCdonuts.co-3.23Compare
.hospitalRuby Pike, LLCdonuts.co-3.23Compare
.insurePioneer Willow, LLCdonuts.co-3.23Compare
.gamesFoggy Beach, LLCdonuts.co-3.23Compare
.financialJust Cover, LLCdonuts.co-3.23Compare
.filmOuter Avenue, LLCdonuts.co-3.23Compare
.charityCorn Lake, LLCdonuts.co-3.23Compare
.attorneyVictor North, LLCdonuts.co-3.23Compare
.creditcardBinky Frostbite, LLCdonuts.co-3.23Compare
.movieNew Frostbite, LLCdonuts.co-3.23Compare
.mortgageOuter Gardens, LLCdonuts.co-3.23Compare
.legalBlue Falls, LLCdonuts.co-3.23Compare
.lawCorn Dynamite, LLCdonuts.co-3.23Compare
.investmentsHolly Glen, LLCdonuts.co-3.23Compare
.healthcareSilver Glen, LLCdonuts.co-3.23Compare
.fundJohn Castle, LLCdonuts.co-3.23Compare
.doctorBrice Trail, LLCdonuts.co-3.23Compare
.creditSnow Shadow, LLCdonuts.co-3.23Compare