AI Services Acceptable Use Policy

Last Update:
March 1, 2026

This AI Acceptable Use Policy (“AI AUP”) supplements the Enterprise Subscription Agreement or other executed agreement entered into between the Parties (the “Agreement”) and governs Customer's use of Customer AI Tools and Customer ML Tools with the Services and Services Data and Customer’s access to and use of the MCP Service, each as expressly permitted under the Agreement or applicable service order. This AI AUP forms part of the Agreement, in the event of any conflict with the other terms and conditions of the Agreement, the terms and conditions of this AI AUP will control. Capitalized terms not defined herein have the meanings set forth in the Agreement.

1. Definitions

“Change of Control” means any merger, consolidation, reorganization, or other transaction where 50% or more of Customer’s voting power is transferred to a third party or (ii) a sale or transfer of all or substantially all of Customers assets or equity.

“Customer AI Tools” means Enterprise GenAI and/or Customer-Managed OSS GenAI, including without limitation, any agentic/orchestration framework, MCP client, or toolchain used to invoke such systems, used by Customer to access the Services or Services Data.

“Customer-Managed OSS GenAI” means an open-source large language model (e.g., Llama, Gemma) deployed and managed solely by Customer, hosted (a) on Customer’s own infrastructure with no external provider retention or training or (b) public cloud infrastructure (e.g. AWS, GCP, Azure) with no external provider retention or training.

“Enterprise GenAI” means a Foundational Model as a Service (defined below) or a third-party generative AI solution (e.g., OpenAI, Google, or Anthropic foundational/agentic models) for which Customer holds enterprise, business, or equivalent licensing that contractually prohibits the provider from (a) using Customer inputs or outputs to train, fine-tune, or improve models and (b) retaining such data beyond ephemeral processing.

“Feed/Bulk Raw Data” means Raw Data provided via bulk exports or feeds (e.g., NOD/NAD, DNSDB Export, DomainTools’ Iris Daily).

"Foundation Model as a Service (FMaaS)" means a cloud-based delivery model that provides access to large-scale, pre-trained Artificial Intelligence (AI) models via APIs (e.g. Amazon Bedrock, Microsoft Azure AI Foundry, or Google Cloud Vertex AI).

“Customer ML Tools” means Customer-developed or -licensed traditional machine learning (“ML”) or deep-learning libraries and applications.

“MCP Service” means DomainTools’ Model Context Protocol interface or other similar interface that may be offered to Customer by DomainTools.

“AI Outputs” means the responses or other results generated by an AI tool based on Customer inputs that incorporate or are derived from Services Data.

“Personal GenAI” means a third-party generative AI solution without enterprise licensing protections against training/retention, where Services Data could be used by the provider to train or improve its models.

“Permitted Purpose” means Customer’s internal security operations relating to cybersecurity, fraud prevention, network and information security, threat detection, prevention, and remediation, law, regulatory, and rights enforcement, and the investigation of illegal acts or threats to safety or security.

“Raw Data” means Services Data that does not include DomainTools’ risk scores or machine-learning-derived outputs (e.g., DNSDB API data, WHOIS/RDAP data, or Iris data without risk scores).

“Risk Score Data” means Services Data that includes risk scores or other machine-learning-derived outputs (e.g., Domain Risk Scores, Risk Feeds, or Hotlists).

“Service(s)” means the DomainTools services to which Customer subscribes under the Agreement or that DomainTools provides to Customer, including any Application Program Interface (“API”), tools, software, code, documentation or other materials provided therewith including the MCP Service if provided by DomainTools.

“Services Data” means data made available to Customer by a Service.

2. Access; Security Controls

2.1 Credentials; Questionnaire. Customer will access MCP Services using only credentials provided by DomainTools. Prior to enabling Customer's access to the MCP Services, or allowing use of any Customer AI Tools or Customer ML Tools with the Services, DomainTools may require Customer to complete a questionnaire regarding Customer's current AI tools/models, intended use cases, and access/security controls.

2.2 Security and Technical Controls. DomainTools may implement rate limits, model allow-lists/deny-lists, content filters, logging and other measures or controls necessary to enforce this AI AUP.

3. Use Requirements and Permitted, Restricted and Prohibited Uses

3.1 Use Requirements. If Customer is expressly permitted to use AI tools or systems under the Agreement, the following requirements apply:

(a) Enterprise GenAI, Customer ML Tools, or Customer-Managed OSS GenAI Only. Customer may only use the Services and Services Data with (i) Enterprise GenAI solutions approved by DomainTools, (ii) Customer-Managed OSS GenAI hosted and controlled by Customer, or (iii) Customer ML Tools hosted and controlled by Customer, in each case subject to this Section 3. Personal GenAI is not permitted.

(b) OSS Guardrails. For Customer-Managed OSS GenAI, Customer must ensure the model is in an isolated environment with no outbound connections and does not allow any training, fine-tuning, or saving of Services Data beyond what is necessary for returning a single response.

(c) No Bulk Ingestion. There may be no bulk ingestion of Raw Data or Risk Score Data into any AI systems except as expressly approved under Section 3.3.

(d) Purpose Limitation. Use must be solely for the Permitted Purpose and in compliance with applicable laws. Any use for the purpose of building or marketing a substitute data product or risk-scoring service is strictly prohibited.

3.2 Permitted Uses. Subject to 3.1 and the Agreement, Customer may:

(a) Customer ML Tools with Raw Data (API and Feeds). Use Raw Data accessed via API or Feed/Bulk Raw Data for Customer’s ML Tools that support internal security operations, provided no models are trained on Risk Score Data and no redistribution occurs.

(b) Enterprise GenAI with API Data. Use Enterprise GenAI with Raw Data or Risk Score Data accessed via API (not feeds) for internal threat analysis, investigation, enrichment, summarization, and workflow automation, provided that the Enterprise GenAI contract prohibits training and retention beyond ephemeral processing.

(c) Customer-Managed OSS GenAI with API Data. Use Customer-Managed OSS GenAI with Raw Data or Risk Score Data accessed via API (not feeds) for internal security purposes in an isolated environment without persistent embeddings or vector stores containing Services Data.

3.3 Restricted Uses – Prior Approval Required. The following uses require DomainTools’ prior written approval and may be subject to additional fees, restrictions, and/or an OEM/derivative-rights license:

(a) Customer ML Tools with Risk Score Data. Using Risk Score Data (via API or feeds at scale) to train or operate Customer’s ML Tools.

(b) GenAI with Feed/Bulk Raw Data and Risk Scores via Feeds. Using Feed/Bulk Raw Data or Risk Score Data delivered via feeds with Enterprise GenAI or Customer-Managed OSS GenAI.

(c) Model-to-Model Benchmarking at Scale. Systematic benchmarking or evaluation that involves large-scale extraction, caching, or replication of Services Data or AI Outputs within AI tools.

To request approval for a restricted use under this Section 3.3, Customer must email the address specified by DomainTools, including a description of the intended use case, AI tools involved, and data types/volumes anticipated. Approval is granted in DomainTools’ sole discretion but will not be unreasonably withheld.

3.4 Prohibited Uses. The following uses are prohibited:

(a) Personal GenAI with Any Services Data. Input any Services Data into Personal GenAI.

(b) Train or Fine-Tune LLMs/GenAI (including RAG). Use Services Data to train, fine-tune, improve, or develop any new AI model or to build retrieval-augmented generation or embeddings stores that persist Services Data or enable model improvement.

(c) Derivative AI Products. Use Services Data to develop, train, or improve any AI-based product or service that competes with DomainTools’ offerings.

(d) Circumvent Limits. Use Customer AI Tools or Customer ML Tools, or any other AI or Customer-controlled systems, to circumvent query limits, rate limits, or other usage restrictions set in the Service Order or by the MCP Service.

(e) Re-Identification/Bypass Redactions. Re-identify, or attempt to re-identify, individuals, bypass RDAP/WHOIS redactions, or otherwise defeat data minimization or access controls.

(f) Redistribute via AI. Use Customer AI Tools or Customer ML Tools to extract, repackage, or redistribute Services Data to third parties.

(g) Other Prohibitions. Use Services or Services Data for any purpose prohibited under the Agreement, including, without limitation, the following: (i) in a way prohibited by law, regulation, governmental order, or decree; (ii) to violate the rights of others; (iii) to disparage or harm the reputation of any third-party, (iv) to try to gain unauthorized access to or disrupt any service, device, data, account or network; (v) to generate, distribute, publish, or facilitate spam, malware, malicious code, or items of a destructive or deceptive nature; or (vi) to harm, disable, interfere with, or circumvent any aspect of the Services or impair anyone else’s use of the Services. Customer may not distribute, sublicense, resell, transfer, or make available the MCP Services or Services Data, or any portion thereof, to or for third parties, in each case unless and except as expressly authorized in the Agreement or a Service Order. Additionally, Customer may not copy, modify, create a derivative work of, reverse engineer, decompile, disassemble, or work around technical limitations in the MCP Service, except to the extent applicable law permits it despite these limitations. Use of any “deep-link,” “page-scrape,” “robot,” “spider” or other automatic device, program, algorithm or methodology, or any similar manual process, to access, acquire, copy, or monitor any portion of the MCP Services, or any Services Data, is prohibited.

4. Outputs; Usage

Customer may use AI Outputs solely for the Permitted Purpose. Customer shall not represent AI Outputs as originating from DomainTools or as DomainTools’ analysis or conclusions, and shall not distribute AI Outputs to third parties except to service providers under confidentiality obligations or as reasonably necessary for law enforcement cooperation, legal proceedings, or regulatory compliance.

5. Telemetry, Monitoring, and Audit Cooperation.

DomainTools may collect and retain telemetry (e.g., timestamps, endpoint, tool/model identifier, token/usage counts, hashed request fingerprints) to enforce entitlements, security, and this AI AUP, and may monitor MCP Service or other Service interface traffic for the same purposes. Except as required for security, audit, or legal compliance, retention of such telemetry will follow DomainTools’ standard practices. In addition to any other audit rights granted to DomainTools under the Agreement, DomainTools may, upon reasonable notice (not less than five (5) business days) and not more than once in any twelve (12) month period, and subject to any reasonable additional obligations of confidentiality that Customer may impose, request information from Customer reasonably necessary to verify Customer’s compliance with this AI AUP, and Customer will cooperate with such requests.

6. MCP Security Requirements

Customer will (a) restrict MCP/API credentials to authorized personnel; (b) use encrypted connections for all MCP Service communications; (c) monitor and log access to the MCP Service; and (d) promptly notify DomainTools of any confirmed unauthorized access to or misuse of the MCP Service and cooperate with DomainTools’ investigation.

7. Data Retention and Deletion

7.1 No Persistent AI/ML Stores. Customer shall not configure Customer AI Tools or Customer ML Tools to create persistent caches, vector databases, embeddings stores, or other repositories of Services Data, except as may be expressly permitted by 3.2 (Permitted Uses) or 3.3 (Restricted Uses) subject to approval. For clarity, this Section 7.1 does not prohibit Customer from storing machine-learning or deep-learning artifacts (e.g., model files) in connection with its permitted or approved uses of Customer ML Tools; provided that (a) any artifacts trained on Risk Score Data require prior approval under Section 3.3(a); (b) artifacts trained on Raw Data remain internal-use only and may not be provided to third parties or used to create a substitute data product or risk-scoring service; and (c) such artifacts are handled in accordance with Section 7.2 and all other applicable obligations under the Agreement.

7.2 Retention over 30 days. To the extent the Customer is expressly authorized under the Agreement, or is permitted under Section 3.2 or 3.3 of this AUP, to persistently store and use Services Data in Customer-controlled systems (“On-Site Customer-Managed Data”), any such data that is accessed through the MCP Service, Customer ML Tools, or Customer AI Tools, and stored by Customer for more than thirty (30) days must comply with the additional security requirements set forth below, together with all other applicable restrictions and obligations under the Agreement:

Customer shall at all times utilize reasonable and appropriate security practices to protect, safeguard, and secure the On-Site Customer-Managed Data against unauthorized access, use or disclosure. Those security practices will include, at a minimum: (a) strong encryption of the full database of On-Site Customer-Managed Data or any significant subset thereof in transit and at rest; (b) segregation of the full database of On-Site Customer-Managed Data or any significant subset thereof from other data (where logical segregation shall be adequate, with implementation of industry standard access controls); (c) ensuring that all computers or servers containing or with access to the On-Site Customer-Managed Data run the current version (including updated virus and threat definitions) of industry standard anti-virus software or intrusion detection software; (d) ensuring that all systems containing the full database of On-Site Customer-Managed Data or any significant subset thereof are protected by fully updated industry-standard firewalls; (e) not placing the full database of On-Site Customer-Managed Data or any significant subset thereof on any portable computer or media; (f) ensuring that only personnel with a need to know for the fulfillment of their duties to Customer will access the On-Site Customer-Managed Data, only to the extent necessary for fulfillment of the duties of such personnel; and (g) establishing and maintaining a system of granular access control (including automatic logging of user access and retention of such logs) to enforce the access limitations described in clause (f).

7.3 Deletion. Upon expiration or termination of the Agreement or of Customer's subscription of the Services, Customer shall promptly delete all Services Data, including any data stored within Customer AI Tools or Customer ML Tools or accessed via the MCP Services, in accordance with the terms of the Agreement.

7.4 Backups and Logs. Customer is not required to alter immutable backups or system logs maintained under standard backup/retention cycles, provided such backups/logs are protected, not used for any purpose other than security, audit, or legal compliance, and are deleted in the ordinary course under those cycles.

8. Suspension

Without limiting any right or remedy DomainTools has under the Agreement or applicable law, DomainTools may immediately suspend access to Services (in whole or part) where (a) it reasonably believes Customer has violated the terms of this AI AUP, (b) there is a security risk or material harm to the Services or Services Data, or (c) such suspension is required by law.

9. Breach and Indemnification

Any breach of this AI AUP by Customer constitutes a material breach of the Agreement and entitles DomainTools to exercise all rights and remedies available under the Agreement and applicable law. Customer will indemnify, defend, and hold harmless DomainTools from any third-party claims arising out of Customer’s violation of this AI AUP.

10. Updates or Modifications to AI AUP

DomainTools may update this AI AUP from time to time. DomainTools will provide Customer with reasonable notice of material changes. Customer’s continued use of Services following such notice constitutes acceptance of the updated AI AUP.

11. Objection on Assignment and Re-Validation

11.1 Notice and Objection Rights. Without limiting any restrictions or conditions on assignment under the Agreement, Customer will provide DomainTools at least thirty (30) days’ prior written notice of any assignment of the Agreement. A Change of Control of Customer will be considered an assignment for purposes of this Section 11. DomainTools may object to an assignment for competitive, regulatory, or legal reasons by written notice within fifteen (15) days after receiving Customer’s notice. If the Parties do not resolve the objection before the assignment, DomainTools may terminate the rights granted under this AI AUP (and, if applicable, any related Services under the Agreement or applicable service order) effective immediately upon the assignment, and DomainTools will refund any prepaid fees for the terminated Services for the post-termination period.

11.2 Re-Validation of Section 3.3 Approvals. Upon any assignment, all approvals previously granted under Section 3.3 automatically lapse unless and until DomainTools re-validates them. Customer will provide information reasonably necessary for re-validation no later than thirty (30) days before the assignment (or promptly upon request). DomainTools may revoke or condition any approval that, in its reasonable judgment, presents material competitive, regulatory, or legal risk.