heykorean.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 56 days left24 years oldTranco #380153
75
heykorean.com was registered on 30 Sep 2002 via GoDaddy.com, LLC and the registry expiry is 30 Sep 2029. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/heykorean.com.
heykorean.com publishes 4 nameservers. DNSSEC is not signed.
heykorean.com has 2 IPv4 addresses (75.2.58.27, 99.83.178.77). The geolocation database places 75.2.58.27 in Seattle, United States.
The TLS certificate from Amazon RSA 2048 M04 is valid and has 56 days left (TLS 1.2). The homepage answered HTTP 200.
Tech detection named Amazon ALB, Amazon Web Services and Nginx. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for heykorean.com in the checks that ran.
Domain · RDAP/WHOIS
heykorean.com was registered on 30 Sep 2002 via GoDaddy.com, LLC. The registry returned 4 status values and 4 nameservers from https://rdap.verisign.com/com/v1/domain/heykorean.com.
| Registered | since 30 Sep 2002 |
|---|---|
| Created | 30 September 2002 |
| Updated | 14 November 2023 |
| Expires | 30 September 2029 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | ns-1249.awsdns-28.org, ns-1809.awsdns-34.co.uk, ns-49.awsdns-06.com, ns-964.awsdns-56.net |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/heykorean.com |
heykorean.com carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.
heykorean.com carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.
heykorean.com carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.
heykorean.com carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
Nameserver ns-1249.awsdns-28.org is published for heykorean.com in the registration record from https://rdap.verisign.com/com/v1/domain/heykorean.com.
Nameserver ns-1809.awsdns-34.co.uk is published for heykorean.com in the registration record from https://rdap.verisign.com/com/v1/domain/heykorean.com.
Nameserver ns-49.awsdns-06.com is published for heykorean.com in the registration record from https://rdap.verisign.com/com/v1/domain/heykorean.com.
Nameserver ns-964.awsdns-56.net is published for heykorean.com in the registration record from https://rdap.verisign.com/com/v1/domain/heykorean.com.
DNS
heykorean.com has 2 address records, 5 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 75.2.58.27, 99.83.178.77 |
|---|---|
| AAAA | — |
| NS | ns-1249.awsdns-28.org, ns-1809.awsdns-34.co.uk, ns-49.awsdns-06.com, ns-964.awsdns-56.net |
| MX | aspmx.l.google.com (1) Google, alt1.aspmx.l.google.com (5) Google, alt2.aspmx.l.google.com (5) Google, alt3.aspmx.l.google.com (10) Google, alt4.aspmx.l.google.com (10) Google |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at heykorean.com is "v=spf1 ip4:123.123.123.123 mx include:_spf.elasticemail.com include:_spf.google.com include:amazonses.com -all".
The DMARC text record at _dmarc.heykorean.com is "v=DMARC1; p=none;".
IPv4 address 75.2.58.27 answers for heykorean.com at resolver 1.1.1.1:53.
IPv4 address 99.83.178.77 answers for heykorean.com at resolver 1.1.1.1:53.
Mail exchanger aspmx.l.google.com has preference 1. The host is recognised as Google.
Mail exchanger alt1.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt2.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt3.aspmx.l.google.com has preference 10. The host is recognised as Google.
Mail exchanger alt4.aspmx.l.google.com has preference 10. The host is recognised as Google.
Hosting and geo
heykorean.com is placed in Seattle, United States by the local geolocation database (db-ip).
| Address | 75.2.58.27 |
|---|---|
| Country | United States |
| City | Seattle |
| Source | db-ip |
SSL/TLS
The certificate for heykorean.com is valid, with 56 days left and 2 subject alternative names. Source: tls:443.
| Issuer | Amazon RSA 2048 M04 |
|---|---|
| Subject | heykorean.com |
| Valid from | 12 June 2026 |
| Valid until | 26 December 2026 |
| Days left | 56 |
| SAN count | 2 |
| Protocol | TLS 1.2 |
| Source | tls:443 |
Subject alternative names: *.heykorean.com, heykorean.com.
Tech stack
Tech detection checked the fetched homepage and named 3 products. Source: wappalyzergo.
- Amazon ALB · Load balancers
- Amazon Web Services · PaaS
- Nginx · Web servers, Reverse proxies
Amazon ALB is filed under Load balancers.
Amazon Web Services is filed under PaaS.
Nginx is filed under Web servers, Reverse proxies.
On-page checks
The homepage returned HTTP 200 in 0 ms. The target title is 0 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 0 ms |
| Title length | 0 no |
| Quoted title | none |
| Meta description | none no |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 0 |
| Images | 0 |
| Favicon | no |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Security
Family DNS for heykorean.com is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
Score breakdown
Availability 25 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 10 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 0 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 15 of 15. Points only when the checks ran and came back clean. Unknown is not clean.
Domain age 5 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: geo city changed from empty to Seattle.
- October 2026: geo country changed from empty to United States.
Questions
Is heykorean.com safe?
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
Who hosts heykorean.com?
heykorean.com is placed in Seattle, United States.
When does heykorean.com expire?
heykorean.com expires on 30 September 2029 according to https://rdap.verisign.com/com/v1/domain/heykorean.com.
Who owns heykorean.com?
The registry did not return a person or a company for heykorean.com. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/heykorean.com at 2026-10-30T13:57:34Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:57:34Z
- TLS source tls:443 at 2026-10-30T13:57:34Z
- HTTP source https://heykorean.com/ at 2026-10-30T13:57:34Z
- Tech source wappalyzergo at 2026-10-30T13:57:34Z
- Geo source db-ip at 2026-10-30T13:57:34Z
- Safety source family DNS and local lists at 2026-10-30T13:57:34Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
Owner of this site?
Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.
How to read this report
The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.