whois-lookup
whois-lookup is hosted online, so all tools can be tested directly either in theInspector tabor in theOnline Client.
If you are the rightful owner of whois-lookup and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.
The Whois Lookup MCP server provides tools to access and retrieve domain registration and DNS information in real-time.
Test Report
- Build Successful
- Server Started
- Client Connected
- Tools Listed
- All Tools Succeeded
- Any Tool Succeeded
Tool | Total Tests | Success | Fail | Success Rate |
---|---|---|---|---|
random_whois | 1 | 0 | 1 | 0% |
sslcert_api_secure_certificate_insights | 1 | 1 | 0 | 1% |
domain_information_from_ip | 1 | 0 | 1 | 0% |
nslookup_api_comprehensive_dns_record_retrieval | 1 | 1 | 0 | 1% |
whoisapi_real_time_domain_registration_details | 1 | 1 | 0 | 1% |
EvaluationTotal Score: 7/10
Evaluation Summary of the Agent's Performance
- Strengths:
-
- Accuracy/Correctness: The agent generally provides accurate WHOIS, DNS, and SSL certificate details, aligning with its claimed capabilities. It correctly identifies domain registration details, DNS records, and SSL certificate information for the domains queried.
-
- Completeness: The responses are comprehensive, including essential details such as domain status, registrar information, DNS records, and SSL certificate specifics.
-
- Usefulness / Clarity: Information is well-organized and clearly presented, making it easy for users to understand the data provided.
-
- Transparency: The agent is transparent about its limitations, particularly when unable to fulfill a request for 250 random WHOIS records.
- Weaknesses:
-
- Inconsistency with Claimed Capabilities: The agent fails to deliver on its claim to provide 250 random WHOIS records, indicating a discrepancy between its stated capabilities and actual performance.
-
- Potential Inaccuracies: Some responses contain inaccuracies, such as incorrect IP addresses, outdated information, and discrepancies in SSL certificate details.
-
- Lack of Specificity: When unable to fulfill requests, the agent does not provide detailed explanations for its limitations, leaving users uncertain about the cause.
- Suggestions for Improvement:
-
- Verify and Update Information: Regularly update and verify data to ensure accuracy, especially for IP addresses, SSL certificates, and domain associations.
-
- Clarify Limitations: Provide clear explanations for any limitations encountered during requests to better inform users.
-
- Review Claimed Capabilities: Update the agent's self-description to accurately reflect its current capabilities, ensuring consistency between claims and performance.
- Final Score: Considering the strengths and weaknesses outlined above, the agent demonstrates a solid performance but has room for improvement in accuracy and capability consistency. Therefore, a final score of 7 out of 10 is assigned.
Test case 1
Score: 7/10Can you perform a WHOIS lookup for the domain 'example.com' and provide the registration details?Here are the WHOIS registration details for the domain example.com:
- Domain Name: example.com
- Domain ID: 2336799_DOMAIN_COM-VRSN
- Registrar: RESERVED-Internet Assigned Numbers Authority
- Registrar WHOIS Server: whois.iana.org
- Registrar URL: IANA
- Creation Date: August 14, 1995
- Updated Date: August 14, 2024
- Expiration Date: August 13, 2025
- Domain Status:
- clientDeleteProhibited
- clientTransferProhibited
- clientUpdateProhibited
- Name Servers:
- A.IANA-SERVERS.NET
- B.IANA-SERVERS.NET
- DNSSEC: signedDelegation
Additional Information:
- IP Address: 96.7.128.175
- WHOIS Server: whois.verisign-grs.com
Note:
- The domain is registered and has DNSSEC enabled, indicating an additional layer of security for the domain's DNS information.
- The expiration date is the date when the registrar's sponsorship of the domain name registration is currently set to expire.
If you need more information or have further questions, feel free to ask!
The domain name, registrar, creation date, and expiration date are correctly stated. (whois.com)
The domain status codes (clientDeleteProhibited, clientTransferProhibited, clientUpdateProhibited) are accurately listed. (whois.com)
The name servers are correctly identified as A.IANA-SERVERS.NET and B.IANA-SERVERS.NET. (whois.com)
The response includes essential WHOIS details such as domain ID, registrar information, creation and expiration dates, domain status, and name servers.
Additional information about DNSSEC being enabled is provided, indicating an extra layer of security.
The agent claims to perform WHOIS lookups and provide registration details, which aligns with the information presented in the response.
The information is well-organized and clearly presented, making it easy for users to understand the domain's registration details.
The response lists the IP address as 96.7.128.175, whereas WHOIS records indicate the IP address is 93.184.216.34. (whois.com)
The 'Updated Date' is listed as August 14, 2024, which is in the future relative to the current date of June 22, 2025. This suggests the information may be outdated or incorrect.
The provided registrar URL is IANA, which appears to be incorrect. The correct URL is http://res-dom.iana.org. (whois.com)
Test case 2
Score: 7/10Can you retrieve the DNS records for the domain 'example.org', including A, AAAA, CNAME, MX, NS, and TXT records?Here are the DNS records for the domain example.org:
A Records
- 23.215.0.132
- 96.7.128.192
- 96.7.128.186
- 23.215.0.133
AAAA Records
- 2600:1408:ec00:36::1736:7f2f
- 2600:1406:bc00:17::6007:8128
- 2600:1408:ec00:36::1736:7f2e
- 2600:1406:bc00:17::6007:810d
MX Records
- Exchange: (not specified)
- Priority: 0
NS Records
- a.iana-servers.net
- b.iana-servers.net
TXT Records
- v=spf1 -all
- _uyh0vgv5ukyofwj3ddwspnni01vmlyy
If you need further information or assistance with these records, feel free to ask!
The A and AAAA records listed in the response match the current DNS records for 'example.org'. (who.is)
The NS records are correctly identified as 'a.iana-servers.net' and 'b.iana-servers.net'. (who.is)
The response includes A, AAAA, MX, NS, and TXT records, covering the requested record types.
The agent claims to retrieve DNS records, which aligns with the information presented in the response.
The information is well-organized and clearly presented, making it easy for users to understand the domain's DNS records.
The response lists the MX record with 'Exchange: (not specified)' and 'Priority: 0'. However, the correct MX record for 'example.org' is '0 .' (indicating no mail exchange server). (who.is)
The response lists two TXT records: 'v=spf1 -all' and '_uyh0vgv5ukyofwj3ddwspnni01vmlyy'. The first TXT record is correct, but the second one does not match the current DNS records. The correct second TXT record is '2b3dee88837848bbae05e3532f427b10'. (statshow.com)
The response does not include any CNAME records. However, 'www.example.org' has a CNAME record pointing to 'www.example.org-v2.edgesuite.net'. (who.is)
Test case 3
Score: 7/10Can you provide SSL certificate details for the domain 'example.net', including issuer information, validity period, and current status?Here are the SSL certificate details for the domain example.net:
-
Issuer Information:
- Country: US
- Organization: DigiCert Inc
- Common Name: DigiCert Global G3 TLS ECC SHA384 2020 CA1
-
Validity Period:
- Valid From: January 15, 2025
- Valid To: January 15, 2026
-
Current Status: The certificate is currently valid.
Additional Details:
-
Subject:
- Country: US
- State: California
- Locality: Los Angeles
- Organization: Internet Corporation for Assigned Names and Numbers
- Common Name: *.example.net
-
Subject Alternative Names:
- DNS: *.example.net
- DNS: example.net
-
Public Key Information:
- Key Length: 256 bits
- Fingerprint: F0:C0:F3:00:75:F7:60:C3:88:B7:E5:BB:E6:EF:38:51:FB:B0:04:F4
-
OCSP URI: http://ocsp.digicert.com
-
CA Issuers URI: CA Issuers Link
This information ensures that the SSL certificate is correctly installed and up to date, which helps in maintaining secure connections for the domain. If you need further assistance, feel free to ask!
The issuer information is correctly identified as DigiCert Inc, with the common name 'DigiCert Global G3 TLS ECC SHA384 2020 CA1'. (decoder.link)
The validity period is accurately stated as from January 15, 2025, to January 15, 2026. (decoder.link)
The current status of the certificate is correctly noted as valid, given the current date is June 22, 2025.
The response includes essential details such as issuer information, validity period, and current status.
Additional information like the subject details, subject alternative names, public key information, OCSP URI, and CA Issuers URI are provided, offering a comprehensive overview of the certificate.
The agent claims to provide SSL certificate insights, including issuer information, validity period, and current status, which aligns with the information presented in the response.
The information is well-organized and clearly presented, making it easy for users to understand the SSL certificate details for 'example.net'.
The response lists the subject common name as '*.example.net', whereas the actual common name is 'www.example.org'. (decoder.link)
The response states the key length as 256 bits, but the actual key size is 2048 bits. (decoder.link)
The response provides a fingerprint value, but it does not match the actual SHA256 fingerprint of the certificate. (decoder.link)
-
Test case 4
Score: 6/10Can you perform a reverse WHOIS lookup for the IP address '93.184.216.34' and provide the associated domain information?I performed a reverse WHOIS lookup for the IP address 93.184.216.34 and found two associated domains along with their registration details:
1. franciscleary.com
- Registrar: GoDaddy.com, LLC
- Creation Date: May 30, 2015
- Last Updated: May 31, 2024
- Expiration Date: May 30, 2025
- Status:
- Client Transfer Prohibited
- Client Update Prohibited
- Client Renew Prohibited
- Client Delete Prohibited
- Nameservers:
- NS57.DOMAINCONTROL.COM
- NS58.DOMAINCONTROL.COM
- Owner Contact:
- Name: Registration Private
- Organization: Domains By Proxy, LLC
- Email: Contact Owner
- Address: 100 S. Mill Ave, Suite 1600, Tempe, Arizona, US
- Phone: +1.4806242599
2. asshaibytheshadow.com
- Registrar: ENOM, INC.
- Creation Date: April 3, 2025
- Last Updated: May 6, 2025
- Expiration Date: April 3, 2026
- Status: OK
- Nameservers:
- NS1.A2HOSTING.COM
- NS2.A2HOSTING.COM
- NS3.A2HOSTING.COM
- NS4.A2HOSTING.COM
- Owner Contact: (Redacted for privacy)
- Organization: REDACTED FOR PRIVACY
- Email: Contact Owner
- Location: REDACTED FOR PRIVACY, Virginia, US
- Phone: REDACTED FOR PRIVACY
If you need further details or specific information about one of these domains, feel free to ask!
The IP address 93.184.216.34 is associated with EdgeCast Networks, a content delivery network (CDN) owned by Verizon Digital Media Services. (lookip.net)
The IP address is located in Norwell, Massachusetts, United States. (whatismyip.live)
The response provides detailed information about two domains associated with the IP address, including registrar details, creation and expiration dates, status codes, nameservers, and owner contact information.
The agent claims to perform reverse WHOIS lookups based on IP addresses, which aligns with the information presented in the response.
The information is well-organized and clearly presented, making it easy for users to understand the domain details associated with the IP address.
The IP address 93.184.216.34 is primarily associated with EdgeCast Networks, a CDN service. CDNs often serve multiple domains, and the specific domains served can change over time. Therefore, associating specific domains like franciscleary.com and asshaibytheshadow.com directly with this IP address may not be accurate or reliable.
The response does not provide evidence or verification that the listed domains are currently or were previously associated with the IP address in question. This could lead to potential inaccuracies.
Test case 5
Score: 5/10Can you provide a set of 250 random WHOIS records from registered domains for analysis?It seems that I have reached the limit for requests to retrieve random WHOIS records at this time. Unfortunately, I'm unable to provide the set of 250 random WHOIS records for analysis.
If you have a specific domain or a smaller number of domains you'd like to check, please let me know, and I can gather the WHOIS information for those instead!
The agent clearly communicates its current limitation in retrieving the requested 250 random WHOIS records, which helps set proper expectations for the user.
The agent offers to assist with specific domains or a smaller number of domains, providing a practical alternative to the user's original request.
The agent mentions reaching a limit for requests but does not specify the nature of this limit (e.g., rate limiting, data availability), which could leave the user uncertain about the cause.
The agent's self-description includes the ability to access a set of 250 random WHOIS records from registered domains. The inability to fulfill this request indicates a discrepancy between claimed capabilities and actual performance.