immy.bot was registered with EnCirca, Inc. on 5 Dec 2017 and is hosted on AS16509 Amazon.com Inc. in United States of America. Its SSL certificate from Google Trust Services LLC expired on 22 Feb 2024, and the site does not support HTTP/3.
What security vendors and the WOT community say about this domain.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
242 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| imrny.digital | Look-alike characters | 21 Sept 2026 | Checking… | Report → |
| 1mmy.top | Look-alike characters | 10 Sept 2026 | Checking… | Report → |
| immy.design | Other extension | 10 Nov 2026 | Checking… | Report → |
| immy.legal | Other extension | 12 Oct 2026 | Checking… | Report → |
| mimy.xyz | Typo | 9 Sept 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is immy.bot’s name taken on other extensions?
3 technologies detected across 3 categories.
Detected from headers, page source and DNS · Automatic and may be incomplete · Suggest a correction
Every IP address immy.bot resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| immy.bot | 44.227.170.101 | 30 |
| Host | Mail server | TTL |
|---|---|---|
| immy.bot | 10 immy-bot.mail.protection.outlook.com | 3600 |
| Host | Name server | TTL |
|---|---|---|
| immy.bot | ns1-03.azure-dns.com | 21600 |
| immy.bot | ns2-03.azure-dns.net | 21600 |
| immy.bot | ns3-03.azure-dns.org | 21600 |
| immy.bot | ns4-03.azure-dns.info | 21600 |
| Host | Text | TTL |
|---|---|---|
| immy.bot | "Foxit-domain-verification=9b82e85090f92c1ed4f1e2d0ac18a7b7" | 60 |
| immy.bot | "google-site-verification=RR7OV5sacVIi7WrrgdsgvND-QfoO7hMTOoND1ripr3g" | 60 |
| immy.bot | "MS=ms83854233" | 60 |
| immy.bot | "proxy-ssl.webflow.com" | 60 |
| immy.bot | "v=spf1 include:_netblocks.immense.net include:21774685.spf08.hubspotemail.net include:spf.protection.outlook.com ip4:104.130.123.22 ip4:166.78.70.182 -all" | 60 |
| Host | Policy | TTL |
|---|---|---|
| immy.bot | 0 iodef mailto:support@immy.bot | 3600 |
| immy.bot | 0 issue digicert.com | 3600 |
| immy.bot | 0 issue letsencrypt.org | 3600 |
| Host | Start of authority | TTL |
|---|---|---|
| immy.bot | ns1-03.azure-dns.com support.immy.bot 1 3600 300 2419200 300 | 3600 |
No reviews yet. Used immy.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.
immy.bot has no community safety rating yet. Its SSL certificate expired on 22 Feb 2024. See Security →
immy.bot is registered through EnCirca, Inc. The owner's details are hidden by a privacy service in the public WHOIS record. See WHOIS →
The registration expired on 5 Dec 2025. See Overview →
immy.bot was registered on 5 Dec 2017, making it 8 years old. See Overview →
immy.bot is served from 1 IP address, mainly on AS16509 Amazon.com Inc. in United States of America. See Hosting →
We detected 3 technologies, including Google Hosted Libraries, Google Analytics and jQuery. See Built with →
Raw registry data for immy.bot. May be redacted by privacy services.
Domain Name: IMMY.BOT
Registry Domain ID: D431F6F8519AF45558B8240CD52665DC7-BOT
Registrar WHOIS Server:
Registrar URL: WWW.ENCIRCA.COM
Updated Date: 2020-09-07T18:43:23Z
Creation Date: 2017-12-05T21:38:03Z
Registry Expiry Date: 2025-12-05T21:38:03Z
Registrar: EnCirca, Inc.
Registrar IANA ID: 455
Registrar Abuse Contact Email: abuse-2024-4@encirca.com
Registrar Abuse Contact Phone: +1.7819429975
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: Immybot, LLC
Registrant Street: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: LA
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: US
Registrant Phone: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Billing ID: REDACTED FOR PRIVACY
Billing Name: REDACTED FOR PRIVACY
Billing Organization: REDACTED FOR PRIVACY
Billing Street: REDACTED FOR PRIVACY
Billing Street: REDACTED FOR PRIVACY
Billing Street: REDACTED FOR PRIVACY
Billing City: REDACTED FOR PRIVACY
Billing State/Province: REDACTED FOR PRIVACY
Billing Postal Code: REDACTED FOR PRIVACY
Billing Country: REDACTED FOR PRIVACY
Billing Phone: REDACTED FOR PRIVACY
Billing Fax: REDACTED FOR PRIVACY
Billing Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: ns1-03.azure-dns.com.
Name Server: ns2-03.azure-dns.net.
Name Server: ns3-03.azure-dns.org.
Name Server: ns4-03.azure-dns.info.
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2023-12-27T01:17:37Z <<<
For more information on Whois status codes, please visit https://icann.org/epp
Amazon Registry Services, Inc. ("Amazon"), the Registry Operator, offers this WHOIS service and provides access to the records in the WHOIS database for information purposes only, to assist you in obtaining information about the registration records of existing domain names. The stored information in the WHOIS database is provided "as is." We do not guarantee its accuracy or completeness, and cannot be held liable if the stored information in the WHOIS database is wrong, incomplete, or inaccurate in any way. By querying the WHOIS database in any way, you agree that you will not use this data: (i) to allow, enable or otherwise support the transmission of unsolicited, commercial advertising or other solicitations in any form or by any means; (ii) to enable high volume, automated, electronic processes that query or send data to Amazon or any registrar; (iii) for target advertising; (iv) to cause nuisance to registrants by sending (by any means) messages to or contacting them; (v) to violate any law, rule, regulation or statute; and/or (vi) in violation of applicable data and privacy protection acts. You are explicitly prohibited from extracting, copying and/or using or re-using in any form and by any means (electronically or not) all or part (quantitatively or qualitatively) of the contents of the WHOIS database without prior and explicit permission from us. Any copying or transmission of data for commercial purposes violates this prohibition. You agree that we can take measures to limit the use of the WHOIS service to protect the privacy of registrants or the integrity of the database. We reserve the right to make changes to this website, the WHOIS service, and these Terms and Conditions at any time without prior notice to you. You should review these Terms and Conditions each time you access or use the WHOIS database and the WHOIS service to learn of any changes. If you do not agree to the changes we have made, your only remedy is to stop your use of the WHOIS database and the WHOIS service. By executing a query, in any means whatsoever, you agree to these Terms and Conditions.The first response from http://www.immy.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 immy.bot. Data is collected independently from public sources and some figures are estimates, provided for information only.
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.
We record what changes from the next time this report is refreshed.