ler.email was registered with whois.nic.email on 2 May 2022 and is hosted on AS6724 in Germany. We couldn't read an SSL certificate for it when we last analysed it.
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.
We couldn't read an SSL certificate on port 443 when we last analysed ler.email. Refresh the analysis to check again.
604 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| 1er.xyz | Look-alike characters | 31 Oct 2026 | Checking… | Report → |
| ier.horse | Look-alike characters | 28 Oct 2026 | Checking… | Report → |
| ier.co.kr | Look-alike characters | 19 Oct 2026 | Checking… | Report → |
| ier.homes | Look-alike characters | 14 Oct 2026 | Checking… | Report → |
| ier.org.ua | Look-alike characters | 11 Oct 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is ler.email’s name taken on other extensions?
Every IP address ler.email resolves to, and where it's hosted.
Other domains served from 81.169.145.92. Normal for shared hosting and CDNs.
No reviews yet. Used ler.email? 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.
ler.email has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
ler.email is registered through whois.nic.email. The owner's details are hidden by a privacy service in the public WHOIS record. See WHOIS →
The registration expired on 2 May 2024. See Overview →
ler.email was registered on 2 May 2022, making it 4 years old. See Overview →
ler.email is served from 1 IP address, mainly on AS6724 in Germany. See Hosting →
Raw registry data for ler.email. May be redacted by privacy services.
{
"rdapConformance": [
"rdap_level_0",
"icann_rdap_response_profile_0",
"icann_rdap_technical_implementation_guide_0"
],
"notices": [
{
"title": "Terms of Service",
"description": [
"Identity Digital Inc. provides this RDAP service for informational purposes only, and to assist persons in obtaining information about or related to a domain name registration record. Identity Digital does not guarantee its accuracy. Users accessing the Identity Digital RDAP service agree to use the data only for lawful purposes, and under no circumstances may this data be used 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 registrar's own existing customers and b) enable high volume, automated, electronic processes that send queries or data to the systems of Identity Digital or any ICANN-accredited registrar, except as reasonably necessary to register domain names or modify existing registrations. When using the Identity Digital RDAP service, please consider the following: the RDAP service is not a replacement for standard EPP commands to the SRS service. RDAP is not considered authoritative for registered domain objects. The RDAP service may be scheduled for downtime during production or OT&E maintenance periods. Queries to the RDAP 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 RDAP service access. Abuse of the RDAP 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 RDAP 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 can be requested by submitting a request via the form found at https://www.identity.digital/about/policies/RDAP-layered-access/ Identity Digital Inc. reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy."
],
"links": [
{
"value": "https://rdap.donuts.co/rdap/domain/ler.email",
"rel": "alternate",
"href": "https://www.identity.digital/about/policies/rdap-access-policy/",
"type": "text/html"
}
]
},
{
"title": "Status Codes",
"description": [
"For more information on domain status codes, please visit https://icann.org/epp"
],
"links": [
{
"value": "https://icann.org/epp",
"rel": "self",
"href": "https://icann.org/epp",
"type": "application/rdap+json"
}
]
},
{
"title": "RDDS Inaccuracy Complaint Form",
"description": [
"URL of the ICANN RDDS Inaccuracy Complaint Form: https://www.icann.org/wicf"
],
"links": [
{
"value": "https://www.icann.org/wicf",
"rel": "self",
"href": "https://www.icann.org/wicf",
"type": "application/rdap+json"
}
]
}
],
"ldhName": "ler.email",
"unicodeName": "ler.email",
"nameservers": [
{
"ldhName": "shades07.rzone.de",
"unicodeName": "shades07.rzone.de",
"objectClassName": "nameserver",
"handle": "5f051ee0bac44c088e04485f2f95d2ea-DONUTS",
"status": [
"associated"
]
},
{
"ldhName": "docks15.rzone.de",
"unicodeName": "docks15.rzone.de",
"objectClassName": "nameserver",
"handle": "2b17783c2414478082e0f1f15a8eaa5a-DONUTS",
"status": [
"associated"
]
}
],
"publicIds": [
{
"type": "IANA Registrar ID",
"identifier": "141"
}
],
"objectClassName": "domain",
"handle": "1979c71f865442209fdb4177e4973eca-DONUTS",
"status": [
"auto renew period"
],
"events": [
{
"eventAction": "expiration",
"eventDate": "2024-05-02T09:25:30.855Z"
},
{
"eventAction": "registration",
"eventDate": "2022-05-02T09:25:30.855Z"
},
{
"eventAction": "last changed",
"eventDate": "2023-05-02T09:25:43.062Z"
},
{
"eventAction": "last update of RDAP database",
"eventDate": "2023-05-12T16:18:35.142Z"
}
],
"entities": [
{
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
]
]
],
"roles": [
"technical",
"administrative"
],
"objectClassName": "entity",
"remarks": [
{
"title": "REDACTED FOR PRIVACY",
"type": "object redacted due to authorization",
"description": [
"Some of the data in this object has been removed."
]
},
{
"title": "EMAIL REDACTED FOR PRIVACY",
"type": "object redacted due to authorization",
"description": [
"Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant of the queried domain name."
]
}
],
"events": [
{
"eventAction": "last update of RDAP database",
"eventDate": "2023-05-12T16:18:35.142Z"
}
]
},
{
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"adr",
{},
"text",
[
"",
"",
"",
"",
"",
"",
"DE"
]
]
]
],
"roles": [
"registrant"
],
"objectClassName": "entity",
"remarks": [
{
"title": "REDACTED FOR PRIVACY",
"type": "object redacted due to authorization",
"description": [
"Some of the data in this object has been removed."
]
},
{
"title": "EMAIL REDACTED FOR PRIVACY",
"type": "object redacted due to authorization",
"description": [
"Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant of the queried domain name."
]
}
],
"events": [
{
"eventAction": "last update of RDAP database",
"eventDate": "2023-05-12T16:18:35.142Z"
}
]
},
{
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"fn",
{},
"text",
"Cronon GmbH"
]
]
],
"roles": [
"registrar"
],
"publicIds": [
{
"type": "IANA Registrar ID",
"identifier": "141"
}
],
"objectClassName": "entity",
"handle": "141",
"entities": [
{
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"tel",
{
"type": "voice"
},
"uri",
"tel:+49.30398020"
],
[
"email",
{},
"text",
"[email protected]"
]
]
],
"roles": [
"abuse"
],
"objectClassName": "entity",
"handle": "2e4437550ef8475ebea8e4044c2c71fb-DONUTS"
}
],
"links": [
{
"value": "https://rdap.donuts.co/rdap/entity/141",
"rel": "self",
"href": "https://rdap.donuts.co/rdap/entity/141",
"type": "application/rdap+json"
}
]
}
],
"links": [
{
"value": "https://rdap.cronon.net/domain/ler.email",
"rel": "related",
"href": "https://rdap.cronon.net/domain/ler.email",
"type": "application/rdap+json"
},
{
"value": "https://rdap.donuts.co/rdap/domain/ler.email",
"rel": "self",
"href": "https://rdap.donuts.co/rdap/domain/ler.email",
"type": "application/rdap+json"
}
]
}The first response from http://www.ler.email, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with ler.email. 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.