beelody.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
HTTP 404SafeSSL: 60 days left6 years old
55
beelody.com was registered on 25 Jul 2020 via Web Commerce Communications Limited dba WebNic.cc and the registry expiry is 25 Jul 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/beelody.com.
beelody.com publishes 2 nameservers. DNSSEC is not signed.
beelody.com has 1 IPv4 address (185.49.85.173). The geolocation database places 185.49.85.173 in Tehran, Iran.
The TLS certificate from YR2 is valid and has 60 days left (TLS 1.3).
Tech detection named LiteSpeed. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for beelody.com in the checks that ran.
Domain · RDAP/WHOIS
beelody.com was registered on 25 Jul 2020 via Web Commerce Communications Limited dba WebNic.cc. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/beelody.com.
| Registered | since 25 Jul 2020 |
|---|---|
| Created | 25 July 2020 |
| Updated | 27 June 2026 |
| Expires | 25 July 2027 |
| Registrar | Web Commerce Communications Limited dba WebNic.cc |
| Status | active |
| Nameservers | rick.ns.cloudflare.com, tina.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/beelody.com |
Nameserver rick.ns.cloudflare.com is published for beelody.com in the registration record from https://rdap.verisign.com/com/v1/domain/beelody.com.
Nameserver tina.ns.cloudflare.com is published for beelody.com in the registration record from https://rdap.verisign.com/com/v1/domain/beelody.com.
DNS
beelody.com has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 185.49.85.173 |
|---|---|
| AAAA | — |
| NS | rick.ns.cloudflare.com, tina.ns.cloudflare.com |
| MX | beelody.com (0) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at beelody.com is "v=spf1 +a +mx +ip4:185.49.84.242 ~all".
IPv4 address 185.49.85.173 answers for beelody.com at resolver 1.1.1.1:53.
Mail exchanger beelody.com has preference 0.
Hosting and geo
beelody.com is placed in Tehran, Iran by the local geolocation database (db-ip).
| Address | 185.49.85.173 |
|---|---|
| Country | Iran |
| City | Tehran |
| Source | db-ip |
SSL/TLS
The certificate for beelody.com is valid, with 60 days left and 5 subject alternative names. Source: tls:443.
| Issuer | YR2 |
|---|---|
| Subject | beelody.com.beelody.net |
| Valid from | 2 October 2026 |
| Valid until | 31 December 2026 |
| Days left | 60 |
| SAN count | 5 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: beelody.com, beelody.com.beelody.net, mail.beelody.com, www.beelody.com, www.beelody.com.beelody.net.
Tech stack
Tech detection checked the fetched homepage and named 1 product. Source: wappalyzergo.
- LiteSpeed · Web servers
LiteSpeed is filed under Web servers.
On-page checks
The homepage returned HTTP 404 in 76 ms. The target title is 13 characters and the page has 1 H1 heading.
| Status | 404 |
|---|---|
| TTFB | 76 ms |
| Title length | 13 yes |
| Quoted title | "404 Not Found" |
| Meta description | none no |
| H1 count | 1 |
| 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 beelody.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 20 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: geo city changed from empty to Tehran.
- October 2026: geo country changed from empty to Iran.
Questions
Is beelody.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 beelody.com?
beelody.com is placed in Tehran, Iran.
When does beelody.com expire?
beelody.com expires on 25 July 2027 according to https://rdap.verisign.com/com/v1/domain/beelody.com.
Who owns beelody.com?
The registry did not return a person or a company for beelody.com. RDAP often redacts the registrant. The registrar on file is Web Commerce Communications Limited dba WebNic.cc.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/beelody.com at 2026-10-30T13:46:32Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:46:32Z
- TLS source tls:443 at 2026-10-30T13:46:32Z
- HTTP source https://beelody.com/ at 2026-10-30T13:46:32Z
- Tech source wappalyzergo at 2026-10-30T13:46:32Z
- Geo source db-ip at 2026-10-30T13:46:32Z
- Safety source family DNS and local lists at 2026-10-30T13:46:32Z
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.