eelly.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafe19 years oldTranco #906004
35
eelly.com was registered on 12 Aug 2007 via Alibaba Cloud Computing (Beijing) Co., Ltd. and the registry expiry is 12 Aug 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/eelly.com.
eelly.com publishes 2 nameservers. DNSSEC is not signed.
eelly.com has 1 IPv4 address (203.107.45.167). The geolocation database places 203.107.45.167 in Hangzhou (Xihu Qu), China.
No safety warning was recorded for eelly.com in the checks that ran.
Domain · RDAP/WHOIS
eelly.com was registered on 12 Aug 2007 via Alibaba Cloud Computing (Beijing) Co., Ltd.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/eelly.com.
| Registered | since 12 Aug 2007 |
|---|---|
| Created | 12 August 2007 |
| Updated | 28 July 2026 |
| Expires | 12 August 2027 |
| Registrar | Alibaba Cloud Computing (Beijing) Co., Ltd. |
| Status | active |
| Nameservers | dns19.hichina.com, dns20.hichina.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/eelly.com |
Nameserver dns19.hichina.com is published for eelly.com in the registration record from https://rdap.verisign.com/com/v1/domain/eelly.com.
Nameserver dns20.hichina.com is published for eelly.com in the registration record from https://rdap.verisign.com/com/v1/domain/eelly.com.
DNS
eelly.com has 1 address record, 2 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 203.107.45.167 |
|---|---|
| AAAA | — |
| NS | dns19.hichina.com, dns20.hichina.com |
| MX | mxbiz1.qq.com (1), mxbiz2.qq.com (2) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at eelly.com is "v=spf1 a mx ptr mx:mxbiz1.qq.com mx:mxbiz2.qq.com include:amazonses.com ~all".
IPv4 address 203.107.45.167 answers for eelly.com at resolver 1.1.1.1:53.
Mail exchanger mxbiz1.qq.com has preference 1.
Mail exchanger mxbiz2.qq.com has preference 2.
A random label under eelly.com also resolved, which means wildcard DNS is on.
Hosting and geo
eelly.com is placed in Hangzhou (Xihu Qu), China by the local geolocation database (db-ip).
| Address | 203.107.45.167 |
|---|---|
| Country | China |
| City | Hangzhou (Xihu Qu) |
| Source | db-ip |
SSL/TLS
No TLS certificate was read for eelly.com on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp 203.107.45.167:443: i/o timeout
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
context deadline exceeded
Security
Family DNS for eelly.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 10 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 0 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 5 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: dns spf changed from v=spf1 include:spf.mail.qq.com ~all to v=spf1 a mx ptr mx:mxbiz1.qq.com mx:mxbiz2.qq.com include:amazonses.com ~all.
- October 2026: geo city changed from empty to Hangzhou (Xihu Qu).
- October 2026: geo country changed from empty to China.
Questions
Is eelly.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 eelly.com?
eelly.com is placed in Hangzhou (Xihu Qu), China.
When does eelly.com expire?
eelly.com expires on 12 August 2027 according to https://rdap.verisign.com/com/v1/domain/eelly.com.
Who owns eelly.com?
The registry did not return a person or a company for eelly.com. RDAP often redacts the registrant. The registrar on file is Alibaba Cloud Computing (Beijing) Co., Ltd..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/eelly.com at 2026-10-30T13:52:56Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:52:56Z
- TLS source tls:443 at 2026-10-30T13:52:56Z
- HTTP source https://eelly.com/ at 2026-10-30T13:52:56Z
- Tech source not available at 2026-10-30T13:52:56Z
- Geo source db-ip at 2026-10-30T13:52:56Z
- Safety source family DNS and local lists at 2026-10-30T13:52:56Z
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.