019.name was registered with whois.nic.name on 30 Mar 2023 and is hosted on AS16509 Amazon.com Inc. in Korea (the Republic of). 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 019.name. Refresh the analysis to check again.
412 similar domains registered in the last 90 days — possible typosquatting or phishing.
| Domain | Why it’s similar | Registered | Status | Report |
|---|---|---|---|---|
| 0l9.top | Look-alike characters | 28 Oct 2026 | Checking… | Report → |
| 0i9.tattoo | Look-alike characters | 13 Oct 2026 | Checking… | Report → |
| 0l9.homes | Look-alike characters | 23 Sept 2026 | Checking… | Report → |
| o19.click | Look-alike characters | 24 Aug 2026 | Checking… | Report → |
| 0l9.xyz | Look-alike characters | 1 Aug 2026 | Checking… | Report → |
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is 019.name’s name taken on other extensions?
Every IP address 019.name resolves to, and where it's hosted.
Other domains served from 13.125.151.40. Normal for shared hosting and CDNs.
No reviews yet. Used 019.name? 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.
019.name has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
019.name is registered through whois.nic.name. The owner's details are hidden by a privacy service in the public WHOIS record. See WHOIS →
The registration expired on 30 Mar 2024. See Overview →
019.name was registered on 30 Mar 2023, making it 3 years old. See Overview →
019.name is served from 5 IP addresses, mainly on AS16509 Amazon.com Inc. in Korea (the Republic of). See Hosting →
Raw registry data for 019.name. May be redacted by privacy services.
{"objectClassName":"domain","handle":"190353416_DOMAIN_NAME-VRSN","ldhName":"019.NAME","links":[{"value":"https:\/\/tld-rdap.verisign.com\/name\/v1\/domain\/019.NAME","rel":"self","href":"https:\/\/tld-rdap.verisign.com\/name\/v1\/domain\/019.NAME","type":"application\/rdap+json"},{"value":"https:\/\/rdap.dotnamekorea.com\/domain\/019.NAME","rel":"related","href":"https:\/\/rdap.dotnamekorea.com\/domain\/019.NAME","type":"application\/rdap+json"}],"status":["active"],"entities":[{"objectClassName":"entity","handle":"1132","roles":["registrar"],"publicIds":[{"type":"IANA Registrar ID","identifier":"1132"}],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text","Dotname Korea Corp."]]],"entities":[{"objectClassName":"entity","roles":["abuse"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""],["tel",{"type":"voice"},"uri","tel:+82.7070900820"],["email",{},"text","[email protected]"]]]}]},{"objectClassName":"entity","roles":["registrant"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""],["org",{},"text","kang seung heui"],["adr",{"cc":"KR"},"text",["","","","","-","",""]]]],"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, Admin, or Tech contact of the queried domain."]}]},{"objectClassName":"entity","roles":["administrative"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""]]],"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, Admin, or Tech contact of the queried domain."]}]},{"objectClassName":"entity","roles":["billing"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""]]],"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, Admin, or Tech contact of the queried domain."]}]},{"objectClassName":"entity","roles":["technical"],"vcardArray":["vcard",[["version",{},"text","4.0"],["fn",{},"text",""]]],"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, Admin, or Tech contact of the queried domain."]}]}],"events":[{"eventAction":"registration","eventDate":"2023-03-30T14:19:04Z"},{"eventAction":"expiration","eventDate":"2024-03-30T14:19:04Z"},{"eventAction":"last changed","eventDate":"2023-03-30T14:19:04Z"},{"eventAction":"last update of RDAP database","eventDate":"2023-05-20T06:44:02Z"}],"secureDNS":{"delegationSigned":false},"nameservers":[{"objectClassName":"nameserver","ldhName":"NS11.DNSTOOL.NET"},{"objectClassName":"nameserver","ldhName":"NS12.DNSTOOL.NET"},{"objectClassName":"nameserver","ldhName":"NS13.DNSTOOL.NET"}],"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.019.name, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with 019.name. 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.