JSON API

Introduction

An API interface has been implemented for four of the tools. It is still in an early beta stage. The API has been made available to gather feedback and to support further development of the website 'under the hood'. At this point, there are still a lot of things missing, but the essentials are there, and the API is working as intended on the selected tools.

At this point, there is no user registration and/or authentication implemented; it will be added at a later point.

Feedback

The main purpose, of pushing the API at this point, is to gather feedback.

I hope you will share any thoughts, ideas and experiences with me.

Mail me at iamrootdottech@gmail.com - looking forward to your input!

Next up

• User signup/registration
• Authentication on the API has to be implemented
• Further tuning of the API, establishing common ground, and developing core concepts.

Please note...

...the API will be subject to changes and updates going forward. I will make sure to detail major changes on this page, and in the sitewide changelog as well.

URL/endpoint structure

The intent is, that the URL structure of each API, has to mirror the URLs used at the website. For instance, the website URL for a WHOIS-lookup of yahoo.com, looks like this:

https://iamroot.tech/whois/?host=yahoo.com&qt=PreferRdap

The matching API request, looks like this:

https://iamroot.tech/whois/api/?host=yahoo.com&qt=PreferRdap

More tool-specific details below.

Authentication and rate limits

No user authentication has been implemented so far - all use of the API is anonymous at this point.

Even though no authentication is implemented, a rate limit of 200 requests per 24 hours apply - and is enforced.

API response wrapper

All API responses share a common JSON object on the root level. It has various status and meta info. Should be pretty straightforward to interpret.

{
    "Status": 200,
    "StatusTxt": "AllGood",
    "Message": null,
    "RequestTimestamp": "2023-10-05T21:04:45.970403Z",
    "RequestServer": "horsens",
    "RequestTool": "whois",
    "RequestUuid": "09b8878f0e054808b89a4e3d125a6d07",
    "RequestExecutionTime": 1084,
    "UserUuid": null,
    "UserApikeyUuid": null,
    "UserQueryLimit24h": 196,
    "DataObjectType": "SslInfoV2Simplified",
    "Data": [...]
}

You may read more about the WHOIS/RDAP tool at https://iamroot.tech/whois/. When using the tool in your browser, the URL of the corresponding API call is mentioned as a part of the result.

Perform WHOIS / RDAP lookup

Samples & output

Lookup of '8.8.8.8', prefer RDAP with failover to WHOIS:

Lookup of 'AS16509', force WHOIS:

You may read more about the TLS/SSL tool at https://iamroot.tech/ssl-certificate-check/. When using the tool in your browser, the URL of the corresponding API call is mentioned as a part of the result.

Perform TLS/SSL certifictae check of host

Samples & output

SSL/TLS check of 'google.com', all default settings:

SSL/TLS check of 'wrong.host.badssl.com', all default settings:

You may read more about the port scan tool at https://iamroot.tech/port-scan/. When using the tool in your browser, the URL of the corresponding API call is mentioned as a part of the result.

Perform port scan of host

Samples & output

Port scan of 'www.db4free.net':

Port scan of 'ftp.gnu.org', with additional check of port 5000:

You may read more about the DNSBL check at https://iamroot.tech/dnsbl-blacklist-checker/. When using the tool in your browser, the URL of the corresponding API call is mentioned as a part of the result.

Perform DNSBL check of host

Samples & output

DNSBL check of 'mail.iamroot.tech':