mybit.me was registered with Key-Systems GmbH on 4 May 2024 and is hosted on AS13238 in Russia. Its SSL certificate from Let's Encrypt expired on 25 Jun 2025.
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.
302 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| myhit.me | Typo | 19 Oct 2026 | Checking… | Report → |
| mybot.me | Typo | 5 Oct 2026 | Checking… | Report → |
| mybit.casino | Other extension | 4 Nov 2026 | Checking… | Report → |
| mybit.si | Other extension | 20 Oct 2026 | Checking… | Report → |
| mybit.tools | Other extension | 10 Oct 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is mybit.me’s name taken on other extensions?
Every IP address mybit.me resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| mybit.me | 213.180.193.247 | 220 |
| Host | IPv6 address | TTL |
|---|---|---|
| mybit.me | 2a02:6b8::1da | 676 |
| Host | Name server | TTL |
|---|---|---|
| mybit.me | ns1.yandexcloud.net | 3600 |
| mybit.me | ns2.yandexcloud.net | 3600 |
| Host | Start of authority | TTL |
|---|---|---|
| mybit.me | ns1.yandexcloud.net mx.cloud.yandex.net 1 10800 900 604800 900 | 3600 |
Other domains served from 213.180.193.247. Normal for shared hosting and CDNs.
No reviews yet. Used mybit.me? 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.
mybit.me has no community safety rating yet. Its SSL certificate expired on 25 Jun 2025. See Security →
mybit.me is registered through Key-Systems GmbH. The owner's details are hidden by a privacy service in the public WHOIS record. See WHOIS →
The registration expired on 4 May 2026. See Overview →
mybit.me was registered on 4 May 2024, making it 2 years old. See Overview →
mybit.me is served from 1 IP address, mainly on AS13238 in Russia. See Hosting →
Raw registry data for mybit.me. May be redacted by privacy services.
Domain Name: mybit.me Registry Domain ID: a36327ac45494bcf8446d512e68096fa-DONUTS Registrar WHOIS Server: whois.rrpproxy.net Registrar URL: http://key-systems.net Updated Date: 2024-11-22T08:22:56Z Creation Date: 2024-05-04T19:11:23Z Registry Expiry Date: 2026-05-04T19:11:23Z Registrar: Key-Systems GmbH Registrar IANA ID: 269 Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +49.68949396850 Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Registry Registrant ID: REDACTED Registrant Name: REDACTED Registrant Organization: c/o whoisproxy.com Registrant Street: REDACTED Registrant City: REDACTED Registrant State/Province: VA Registrant Postal Code: REDACTED Registrant Country: US Registrant Phone: REDACTED Registrant Phone Ext: REDACTED Registrant Fax: REDACTED Registrant Fax Ext: REDACTED Registrant Email: REDACTED Registry Admin ID: REDACTED Admin Name: REDACTED Admin Organization: REDACTED Admin Street: REDACTED Admin City: REDACTED Admin State/Province: REDACTED Admin Postal Code: REDACTED Admin Country: REDACTED Admin Phone: REDACTED Admin Phone Ext: REDACTED Admin Fax: REDACTED Admin Fax Ext: REDACTED Admin Email: REDACTED Registry Tech ID: REDACTED Tech Name: REDACTED Tech Organization: REDACTED Tech Street: REDACTED Tech City: REDACTED Tech State/Province: REDACTED Tech Postal Code: REDACTED Tech Country: REDACTED Tech Phone: REDACTED Tech Phone Ext: REDACTED Tech Fax: REDACTED Tech Fax Ext: REDACTED Tech Email: REDACTED Name Server: ns2.yandexcloud.net Name Server: ns1.yandexcloud.net DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form: https://icann.org/wicf/ >>> Last update of WHOIS database: 2025-05-24T04:31:19Z <<< For more information on Whois status codes, please visit https://icann.org/epp Terms of Use: Access to WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the registry database. The data in this record is provided by Identity Digital or the Registry Operator for informational purposes only, and accuracy is not guaranteed. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Identity Digital except as reasonably necessary to register domain names or modify existing registrations. When using the Whois service, please consider the following: The Whois service is not a replacement for standard EPP commands to the SRS service. Whois is not considered authoritative for registered domain objects. The Whois service may be scheduled for downtime during production or OT&E maintenance periods. Queries to the Whois services are throttled. If too many queries are received from a single IP address within a specified time, the service will begin to reject further queries for a period of time to prevent disruption of Whois service access. Abuse of the Whois system through data mining is mitigated by detecting and limiting bulk query access from single sources. Where applicable, the presence of a [Non-Public Data] tag indicates that such data is not made publicly available due to applicable data privacy laws or requirements. Should you wish to contact the registrant, please refer to the Whois records available through the registrar URL listed above. Access to non-public data may be provided, upon request, where it can be reasonably confirmed that the requester holds a specific legitimate interest and a proper legal basis for accessing the withheld data. Access to this data provided by Identity Digital can be requested by submitting a request via the form found at https://www.identity.digital/about/policies/whois-layered-access/. The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Identity Digital Inc. and Registry Operator reserve the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with mybit.me. 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.