MXToolbox, worked by an AI employee
Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your MXToolbox account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.
- Server Monitoring
- Connects with a key
- 13 ready-made tools
- Asked in Slack or Teams
An illustration of how the conversation reads, not a transcript from a client account.
What MXToolbox is
MxToolbox provides a suite of network diagnostic and monitoring tools, including DNS lookups, blacklist checks, and email health analysis.
You paste in a key from your own MXToolbox account. It is kept encrypted, and you can withdraw it from inside MXToolbox whenever you like.
One message in, the work done in MXToolbox.
- 01
You ask
You message your AI employee in the chat your team already has open, in one sentence, in your own words.
- 02
It works out the step
It decides what the job needs in MXToolbox. You do not pick anything from a menu or wire anything together.
- 03
It does the work
Signed in to your own MXToolbox account, inside the access you granted it, doing the thing you asked for.
- 04
It reports back
It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.
What it can do in MXToolbox
These are the ready-made tools your AI employee already has in MXToolbox. It is not limited to them, but it never has to be taught these.
- Check UsageTool to retrieve api usage statistics. use when you need to monitor remaining api calls and quota reset timing.
- HTTP LookupTool to perform an http test on a domain. use when you need to assess http connectivity and status for a given domain.
- Lookup BIMI RecordTool to retrieve bimi (brand indicators for message identification) record for a domain. use when checking domain brand identity via bimi lookup.
- Lookup BlacklistTool to perform a blacklist check on a domain or ip. use when you need to verify whether a domain or ip is listed in common blacklists.
- Lookup DKIM RecordTool to retrieve dkim records for a domain. use when verifying dkim configuration before sending email.
- Lookup DMARC RecordTool to retrieve dmarc records for a domain. use after confirming the domain is correctly formatted.
- Lookup DNS RecordsTool to retrieve dns records for a given domain. use when you need dns lookup details.
- Lookup MTA-STS RecordTool to lookup mta-sts record for a domain. use when validating mail transport security policy.
- Lookup MX RecordsTool to retrieve mx records for a given domain. use when you need to discover mail exchange servers after obtaining a domain.
- Lookup SPF RecordTool to retrieve spf records for a specified domain. use when confirming email sender authorization policies.
- Monitor StatusTool to retrieve all monitor statuses. use when you need to get current health details of all account monitors.
- Ping LookupTool to perform a ping test on a specified domain or ip address. use when you need hop-by-hop network latency diagnostics.
- SMTP LookupTool to perform an smtp test on the specified domain. use when verifying smtp connectivity for a domain.
You stay the boss of your MXToolbox account.
Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.
How we handle your data- It signs in to your own MXToolbox account. You are not moving anything into ours.
- You grant access one app at a time, and you can take it back the same way.
- Everything it does in MXToolbox is written down, with what it did and when.
- Anything you tell it to check with you first, it checks with you first.
It works in MXToolbox and the rest of your software in the same job
A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.
Questions people ask about MXToolbox
- Can an AI employee really work inside MXToolbox?
- Yes. It signs in to your own MXToolbox account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
- Do I have to move anything out of MXToolbox?
- No. Nothing moves and nothing is replaced. Your records stay in MXToolbox, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
- How does it get into my MXToolbox account?
- You paste in a key from your own MXToolbox account. It is kept encrypted, and you can withdraw it from inside MXToolbox whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
- What can it actually do in MXToolbox?
- It has 13 ready-made tools in MXToolbox today, among them Check Usage, HTTP Lookup and Lookup BIMI Record. The full list is on this page. It is not limited to those, but it never has to be taught them.
- Can it use MXToolbox and the rest of my software in the same job?
- Yes, and that is usually the point. Reading a message in one app, checking a record in MXToolbox and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
- Who decides what it is allowed to do in MXToolbox?
- You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in MXToolbox is written down with what it did and when.