Alternatives to diehl.com
Matched automatically on description, category and technology. Only sites that pass our safety checks are shown. · Report a wrong match
diehl.com was registered on 15 May 1996 and is hosted on AS25115 DIEHL Informatik GmbH in Germany. We couldn't read an SSL certificate for it when we last analysed it. WOT's community rates its safety good (66/100).
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 diehl.com. Refresh the analysis to check again.
80 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| dihel.com | Typo | 10 Nov 2026 | Checking… | Report → |
| idehl.com | Typo | 10 Oct 2026 | Checking… | Report → |
| diehl.consulting | Other extension | 20 Oct 2026 | Checking… | Report → |
| diehll.com | Extra letter | 1 Oct 2026 | Checking… | Report → |
| diehl.rocks | Other extension | 28 Sept 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is diehl.com’s name taken on other extensions?
Estimated visitors and engagement.
| Top countries | Share | Visits | Desktop | Mobile |
|---|---|---|---|---|
| Germany | 62.5% | — | — | — |
| Canada | 14.3% | — | — | — |
| France | 4.3% | — | — | — |
| Poland | 2.5% | — | — | — |
| United States | 2.1% | — | — | — |
Every IP address diehl.com resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| diehl.com | 193.201.238.43 | 86398 |
| Host | Mail server | TTL |
|---|---|---|
| diehl.com | 10 enterprise01.smtp.diehl.com | 86400 |
| diehl.com | 10 enterprise02.smtp.diehl.com | 86400 |
| Host | Name server | TTL |
|---|---|---|
| diehl.com | ns.diehl.com | 86400 |
| diehl.com | ns01.diehl.com | 86400 |
| diehl.com | ns02.diehl.com | 86400 |
| diehl.com | ns10.managed-ip.com | 86400 |
| diehl.com | ns11.managed-ip.info | 86400 |
| diehl.com | ns12.managed-ip.info | 86400 |
| Host | Text | TTL |
|---|---|---|
| diehl.com | "adobe-sign-verification=9785d981ac74a329122ad601f1de0c4d" | 3600 |
| diehl.com | "ca3-a472567651b5440b8b81fcb6674f82c0" | 3600 |
| diehl.com | "ca3-f7609326720a495b86bc90fe5cceaa88" | 3600 |
| diehl.com | "docusign=b0b685c8-f86c-4eee-bc22-7e3f727038e4" | 3600 |
| diehl.com | "MS=ms74426895" | 3600 |
| diehl.com | "v=spf1 mx -all" | 3600 |
| Host | Start of authority | TTL |
|---|---|---|
| diehl.com | ns.diehl.com hostmaster.diehl.com 2023070701 14400 1800 1209600 3600 | 86400 |
No reviews yet. Used diehl.com? 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.
WOT's community rates diehl.com good for safety (66/100). We couldn't read an SSL certificate on it when we last analysed it. See Security →
The registration expired on 16 May 2024. See Overview →
diehl.com was registered on 15 May 1996, making it 30 years old. See Overview →
diehl.com is served from 1 IP address, mainly on AS25115 DIEHL Informatik GmbH in Germany. See Hosting →
Raw registry data for diehl.com. May be redacted by privacy services.
{"objectClassName":"domain","handle":"1659317_DOMAIN_COM-VRSN","ldhName":"DIEHL.COM","links":[{"value":"https:\/\/rdap.verisign.com\/com\/v1\/domain\/DIEHL.COM","rel":"self","href":"https:\/\/rdap.verisign.com\/com\/v1\/domain\/DIEHL.COM","type":"application\/rdap+json"},{"value":"https:\/\/rdap.psi-usa.info\/domain\/DIEHL.COM","rel":"related","href":"https:\/\/rdap.psi-usa.info\/domain\/DIEHL.COM","type":"application\/rdap+json"}],"status":["client transfer prohibited"],"entities":[{"objectClassName":"entity","handle":"151","roles":["registrar"],"publicIds":[{"type":"IANA Registrar ID","identifier":"151"}],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text","PSI-USA, Inc. dba Domain Robot"]]],"entities":[{"objectClassName":"entity","roles":["abuse"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""],["tel",{"type":"voice"},"uri","tel:+49.94159559482"],["email",{},"text","domain-abuse@psi-usa.info"]]]}]}],"events":[{"eventAction":"registration","eventDate":"1996-05-15T04:00:00Z"},{"eventAction":"expiration","eventDate":"2024-05-16T04:00:00Z"},{"eventAction":"last changed","eventDate":"2022-07-11T12:20:11Z"},{"eventAction":"last update of RDAP database","eventDate":"2023-07-11T22:25:16Z"}],"secureDNS":{"delegationSigned":false},"nameservers":[{"objectClassName":"nameserver","ldhName":"NS.DIEHL.COM"},{"objectClassName":"nameserver","ldhName":"NS01.DIEHL.COM"},{"objectClassName":"nameserver","ldhName":"NS02.DIEHL.COM"},{"objectClassName":"nameserver","ldhName":"NS10.MANAGED-IP.COM"},{"objectClassName":"nameserver","ldhName":"NS11.MANAGED-IP.INFO"},{"objectClassName":"nameserver","ldhName":"NS12.MANAGED-IP.INFO"}],"rdapConformance":["rdap_level_0","icann_rdap_technical_implementation_guide_0","icann_rdap_response_profile_0"],"notices":[{"title":"Terms of Use","description":["Service subject to Terms of Use."],"links":[{"href":"https:\/\/www.verisign.com\/domain-names\/registration-data-access-protocol\/terms-service\/index.xhtml","type":"text\/html"}]},{"title":"Status Codes","description":["For more information on domain status codes, please visit https:\/\/icann.org\/epp"],"links":[{"href":"https:\/\/icann.org\/epp","type":"text\/html"}]},{"title":"RDDS Inaccuracy Complaint Form","description":["URL of the ICANN RDDS Inaccuracy Complaint Form: https:\/\/icann.org\/wicf"],"links":[{"href":"https:\/\/icann.org\/wicf","type":"text\/html"}]}]}The first response from http://www.diehl.com, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with diehl.com. 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.