Login / signup

User the form below for both login and / or signup. The form will - regardless of having an account or not - guide you thrugh the process.

EASY

Signup using Google Continue using
Google
 
Signup using Microsoft Continue using
Microsoft
 
Signup using Facebook Continue using
Facebook
 
Signup using Github Continue using
Github
 
OR


About the usersystem


Open beta: The user and monitoring system of iamroot.tech

The system is still in a very early beta. Unforseen issues, errors and interruptions is to be expected. Please be aware of this.

Introduction

The iamroot.tech user and monitoring system allows you to put your lookups, checks, and monitoring tasks on autopilot. There are several pre-cooked and ready-to-use monitors available.

Create your account right away - I've made it as easy as possible. No need for credit cards or anything. To get you started, you'll have a rate limit of 1,000 requests per 24 hours.

You get:
  • An unlimited number of monitors
  • An unlimited number of API keys for your own use
  • A rate limit of 1.000 requests per 24 hours, free of charge

The current set of available monitors:

Port scan
Keep track of changes in accisible TCP/IP ports on any given domain and/or IP. This is a great way to monitor service availiblilty/connectivity as well. You may choose between check frequencis from once every 60 seconds, to once every 24 hours.


WHOIS
Keep track of changes to domain/IP whois info. Great way to keep track of publicly availible info - and to be warned about upcomming domain expirations.


TLS/SSL
The monitor will keep track of changes, upcoming certificate expirations, and renewals. Never miss a TLS certificate expiration again.


DNS propagation
This monitor will track DNS records of the primary / authoritative nameserver and alert you in case of changes. It will also monitor the subsequent propagation of the records. Let the monitor handle the tracking instead of doing endless and repetitive DNS lookups during the propagation period. As a first - ever, this monitor offers a 10 - second check frequency.


What is the catch?

As the monitors work on top of the API, using the monitors will affect the rate limit usage. For instance, having a monitor running a check every 15 minutes will use up 96 requests per 24 hours.

This approach allows both you and me to be completely indifferent about the number of API keys, monitors, and any check frequencies, as all that matters is the 24-hour rate limit.

Upgrading or increasing your rate limit is not an option at the moment (it will be at a later point, though).


Roadmap / changelog

I have a dedicated page for roadmap / changelog of the user system availible here.

New features inbound 🚀
Within a couple of weeks, I'll launch a couple of new awesome features. Signup for the newsletter to stay updated, and get early access as a beta tester.

Signup using Google, Microsoft or Facebook .