Held at 59: the WOT community advises caution.
json.bot was registered on 12 Nov 2015 and is hosted on AS16509 Amazon.com Inc. in United States of America. Its SSL certificate from Let's Encrypt is valid until 30 Nov 2026, and the site does not support HTTP/3.
On-page basics for the homepage.
Networks cache previews — changes can take time to show.
What security vendors and the WOT community say about this domain.
0 of 5 protections set up
No SPF record: any server can send mail that claims to come from this domain.
—No key at the 12 common selectors we checked. A custom selector can’t be found from DNS alone.
—No DMARC policy: receivers aren’t told what to do with mail that fails SPF and DKIM.
—Forces encrypted delivery between mail servers.
—Shows the brand logo in supporting inboxes. Optional; needs DMARC enforcement.
—Read from the domain's public DNS records.
4 of 6 recommended headers
The page is served over plain HTTP, so HTTPS can’t be enforced.
Limits where scripts can load from — the main defence against XSS.
Stops the site being framed for clickjacking.
Prevents browsers guessing file types.
Which AI crawlers this site allows in robots.txt.
From robots.txt. “Partly blocked”: kept out of some pages, not the homepage. Not every crawler follows it.
Pages and files that show who runs the site and how it handles data.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
Internet standards that make a site faster and safer.
The path from a typed address to the final page.
Is json.bot’s name taken on other extensions?
1 technology detected across 1 category.
Detected from headers, page source and DNS · Automatic and may be incomplete · Suggest a correction
Every IP address json.bot resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| json.bot | 44.232.173.249 | 1200 |
| json.bot | 52.40.42.113 | 1200 |
| Host | Name server | TTL |
|---|---|---|
| json.bot | launch1.spaceship.net | 1800 |
| json.bot | launch2.spaceship.net | 1800 |
| Host | Start of authority | TTL |
|---|---|---|
| json.bot | launch1.spaceship.net support.spaceship.com 1788274599 43200 3600 604800 3600 | 1800 |
| Host | Value | TTL |
|---|---|---|
| json.bot | 256 3 13 HwiX9vq3enBRJtCB1AcMnuefaRxhCZAhlvCMocIJjJ+rJG2F2cU8s/xO7UJV/npD0WbtaJeBKcNzHJ8payDfPg== | 3600 |
| json.bot | 257 3 13 s+yudxgP0q+KypIiUM3twER9UrQ/vrwnHWHu2DRINVKfji75VkihpBsAVlrsC7dyM0iUm4GHEhYbvRkbStXdsg== | 3600 |
Other domains served from 52.40.42.113. Normal for shared hosting and CDNs.
No reviews yet. Used json.bot? Be the first to say how it went.
Reviews are from CubDomain users and are separate from the security verdicts above.
Common questions, answered from this report's data.
json.bot has no community safety rating yet. Its SSL certificate is valid until 30 Nov 2026. See Security →
json.bot was registered on 12 Nov 2015, making it 10 years old. See Overview →
json.bot is served from 2 IP addresses, mainly on AS16509 Amazon.com Inc. in United States of America. See Hosting →
We detected 1 technology, including jQuery UI. See Built with →
Raw registry data for json.bot. May be redacted by privacy services.
% IANA WHOIS server % for more information on IANA, visit http://www.iana.org % This query returned 1 object domain: BOT organisation: Amazon Registry Services, Inc. address: 410 Terry Avenue North address: Seattle WA 98109 address: United States of America (the) contact: administrative name: Program Manager, Registry organisation: Amazon Registry Services, Inc. address: 410 Terry Avenue North address: Seattle WA 98109 address: United States of America (the) phone: +1 206 646 5990 fax-no: +1 206 946 7702 e-mail: [email protected] contact: technical name: TLD Registry Services Technical organisation: Nominet address: Minerva House address: Edmund Halley Road address: Oxford Science Park address: Oxford OX4 4DQ address: United Kingdom of Great Britain and Northern Ireland (the) phone: +44.1865332211 e-mail: [email protected] nserver: DNS1.NIC.BOT 213.248.218.55 2a01:618:402:0:0:0:0:55 nserver: DNS2.NIC.BOT 103.49.82.55 2401:fd80:402:0:0:0:0:55 nserver: DNS3.NIC.BOT 213.248.222.55 2a01:618:406:0:0:0:0:55 nserver: DNS4.NIC.BOT 2401:fd80:406:0:0:0:0:55 43.230.50.55 nserver: DNSA.NIC.BOT 156.154.100.3 2001:502:ad09:0:0:0:0:3 nserver: DNSB.NIC.BOT 156.154.101.3 2001:502:2eda:0:0:0:0:3 nserver: DNSC.NIC.BOT 156.154.102.3 2610:a1:1009:0:0:0:0:3 nserver: DNSD.NIC.BOT 156.154.103.3 2610:a1:1010:0:0:0:0:3 ds-rdata: 58741 8 2 eca26804355a4735caa906601c7d388af755ab40f599d02f29d16f347705ee42 whois: status: ACTIVE remarks: Registration information: http://www.nic.bot created: 2015-11-12 changed: 2025-02-14 source: IANA
The first response from http://www.json.bot, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with json.bot. Data is collected independently from public sources and some figures are estimates, provided for information only.
Controls how much of the URL is shared with other sites.
Restricts camera, microphone and other browser features.
From the homepage's response, http://json.bot/
Spam and malware blocklists for the site's IP and mail servers.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.
When the site first appeared, and what has changed since.
No changes seen since we started recording on 26 Oct 2026.