OnlineCyberTools MCP (280+ filterable tools)

osint_domain_age

Check a domain's age, registration date, and expiry from live WHOIS data to evaluate trustworthiness and registration lifecycle. Returns age in days and human-readable string, registrar, name servers, and status.

Instructions

Domain Age Checker. Check a domain's age and registration lifecycle from live WHOIS data: creation/registration date, expiry date, computed age (in days plus a human string like "5 years, 2 months"), registrar, name servers, domain status, and whether privacy/proxy protection is in use. Sends an outbound WHOIS lookup at call time (port 43 to whois.iana.org / whois.internic.net / whois.verisign-grs.com, with an HTTP WHOIS-API fallback), so it reaches the public network and results reflect live registry state. Use this when you specifically want age/expiry/trust signals for a single domain; use network_whois for the full raw registration record of a domain or IP, and network_dns for live DNS records. Read-only and non-destructive but not idempotent (registry data and computed age change over time). CAPTCHA-gated and rate-limited (anonymous 5/min, 30/hour, 100/day). Returns a result object with the parsed fields plus an analysis list of trust/expiry notes and the raw WHOIS text.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`domain`	Yes	Domain name to check, without a URL path, for example youtube.com. A leading http:// or https:// scheme, a trailing path, and a :port are stripped before lookup; the host must be a valid dotted domain.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`success`	No	True when the request was processed (the WHOIS lookup itself may still have partially failed; check result.error).
`result`	No	Parsed domain-age report.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.5.1Jun 3, 2026

changedInput schema / properties / domain / description

Previous value: -"Domain name to check, without a URL path, for example youtube.com."New value: +"Domain name to check, without a URL path, for example youtube.com. A leading http:// or https:// scheme, a trailing path, and a :port are stripped before lookup; the host must be a valid dotted domain."

removedInput schema / properties / domain / examples
```
Removed value: -[
-  "youtube.com"
-]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "description": "Parsed domain-age report.",
+      "properties": {
+        "age_formatted": {
+          "description": "Human-readable age, e.g. 5 years, 2 months or 12 days.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "age_in_days": {
+          "description": "Whole days between registration_date and now; null if no registration date.",
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "analysis": {
+          "description": "Derived trust/expiry/registration notes.",
+          "items": {
+            "properties": {
+              "category": {
+                "description": "Note category, e.g. Domain Age, Domain Status, Registration, Privacy, DNS.",
+                "type": "string"
+              },
+              "message": {
+                "description": "Human-readable explanation of the note.",
+                "type": "string"
+              },
+              "type": {
+                "description": "Severity: success, info, warning, or error.",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "domain": {
+          "description": "Normalized domain that was queried (lowercased, scheme/path/port stripped).",
+          "type": "string"
+        },
+        "error": {
+          "description": "Present only when the WHOIS lookup threw; the exception message.",
+          "type": "string"
+        },
+        "expiration_date": {
+          "description": "Expiration date promoted to top level, Y-m-d H:i:s.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "name_servers": {
+          "description": "Authoritative name servers promoted to top level.",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "privacy_protected": {
+          "description": "True if privacy protection was detected; null if unknown.",
+          "type": [
+            "boolean",
+            "null"
+          ]
+        },
+        "raw_whois": {
+          "description": "Raw WHOIS text returned by the upstream server/API.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "registrar": {
+          "description": "Registrar name promoted to top level.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "registration_date": {
+          "description": "Registration date promoted to top level, Y-m-d H:i:s.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "status": {
+          "description": "Domain status: the string unknown before parsing, otherwise the array of WHOIS status codes.",
+          "type": [
+            "string",
+            "array"
+          ]
+        },
+        "whois_data": {
+          "description": "Structured fields parsed out of the raw WHOIS text; null if parsing produced nothing.",
+          "properties": {
+            "contact_info": {
+              "description": "Registrant/admin/tech/billing contact lines keyed by WHOIS field name.",
+              "type": "object"
+            },
+            "dnssec": {
+              "description": "DNSSEC status from WHOIS, e.g. unsigned.",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "expiration_date": {
+              "description": "Expiry/renewal date, normalized to Y-m-d H:i:s.",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "name_servers": {
+              "description": "Authoritative name servers listed in WHOIS.",
+              "items": {
+                "type": "string"
+              },
+              "type": "array"
+            },
+            "privacy_protected": {
+              "description": "True if a privacy/proxy/WhoisGuard service was detected.",
+              "type": "boolean"
+            },
+            "registrar": {
+              "description": "Registrar name from the WHOIS record.",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "registration_date": {
+              "description": "Creation/registration date, normalized to Y-m-d H:i:s.",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "status": {
+              "description": "Domain status codes, e.g. clientTransferProhibited.",
+              "items": {
+                "type": "string"
+              },
+              "type": "array"
+            },
+            "updated_date": {
+              "description": "Last-updated date, normalized to Y-m-d H:i:s.",
+              "type": [
+                "string",
+                "null"
+              ]
+            }
+          },
+          "type": [
+            "object",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "success": {
+      "description": "True when the request was processed (the WHOIS lookup itself may still have partially failed; check result.error).",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0May 31, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses outbound network access, CAPTCHA gating, rate limits, and non-idempotency. Adds context beyond annotations (e.g., live registry state, returned fields). No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is comprehensive but slightly verbose. However, all information is necessary and front-loaded with purpose, making it well-structured for an AI agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity, the description covers purpose, behavior, params, output (parsed fields, analysis, raw text), and limitations. Output schema exists but description still adds value.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for one parameter. Description adds value by explaining stripping of schemes/paths and requirement for valid dotted domain, beyond the schema description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly specifies the verb 'check' and resource 'domain's age and registration lifecycle' with specific data points. It differentiates from siblings by naming alternative tools (network_whois, network_dns) and their uses.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use this tool vs alternatives, provides prerequisites (domain without path), and details behavior like live WHOIS lookup, rate limits, and non-idempotency.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server