rende.com - dns.ninja
rende.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.ename.net ⚠️ Not in zone NS records | ||||||
| A | 2001:df2:f080:1::8🇭🇰 HKCICL-AS-AP2001:df2:f080::/48 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED | ||||||
| A | 61.158.128.31🇨🇳 CHINA169-Backbone61.158.128.0/17 CNC Group CHINA169 Henan Province Network | ||||||
| PTR | 31.128.158.61.ha.cnc | ||||||
| A | 218.98.111.173🇩🇪 HKCICL-AS-AP218.98.111.0/24 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED | ||||||
| NS | ns2.ename.net ⚠️ Not in zone NS records | ||||||
| A | 240e:97d:10:1402:0:1:0:1005🇨🇳 CHINANET-Guangdong-DongGuan-IDC240e:97d::/36 DongGuan IDC Network | ||||||
| A | 1.193.216.198🇨🇳 CHINANET-Henan-Luoyang-IDC1.193.216.0/24 Chinatelecom HeNan Province Network | ||||||
| A | 183.253.57.199🇨🇳 CHINAMOBILE-CN183.253.0.0/16 CMI (Customer Route) | ||||||
| A | 211.99.99.52🇨🇳 DONGGUAN-1211.99.99.0/24 | ||||||
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1785916454 | ||||||
Same first word
rende.com.tw |
rende.com |
rende.tv |
rende.com.ar |
rende.vu |
rende.nl |
rende.me |
rende.info |
rende.it |
rende.co.th |
rende.ru |
rende.org |
rende.biz |
rende.de |
rende.ca |
rende.gov.tw |
rende.red |
rende.lu |
rende.es |
rende.com.br |
Similar names
DNS History
16 records (2 active, 14 former)
○NSdns1.iidns.com2016-09-11 → 2016-12-08 · 5 obs
○ 2015-11-26 01:10:00
● 2016-09-11 02:42:20
● 2016-12-08 19:10:30
○ 2018-05-29 19:22:58
○ 2026-08-05 08:13:12
● 2016-09-11 02:42:20
● 2016-12-08 19:10:30
○ 2018-05-29 19:22:58
○ 2026-08-05 08:13:12
○NSdns2.iidns.com2016-09-11 → 2016-12-08 · 5 obs
○ 2015-11-26 01:10:00
● 2016-09-11 02:42:20
● 2016-12-08 19:10:30
○ 2018-05-29 19:22:58
○ 2026-08-05 08:13:12
● 2016-09-11 02:42:20
● 2016-12-08 19:10:30
○ 2018-05-29 19:22:58
○ 2026-08-05 08:13:12
○NSdns3.iidns.com2016-09-11 → 2016-12-08 · 5 obs
○ 2015-11-26 01:10:00
● 2016-09-11 02:42:20
● 2016-12-08 19:10:30
○ 2018-05-29 19:22:58
○ 2026-08-05 08:13:12
● 2016-09-11 02:42:20
● 2016-12-08 19:10:30
○ 2018-05-29 19:22:58
○ 2026-08-05 08:13:12
○NSdns4.iidns.com2016-09-11 → 2016-12-08 · 5 obs
○ 2015-11-26 01:10:00
● 2016-09-11 02:42:20
● 2016-12-08 19:10:30
○ 2018-05-29 19:22:58
○ 2026-08-05 08:13:12
● 2016-09-11 02:42:20
● 2016-12-08 19:10:30
○ 2018-05-29 19:22:58
○ 2026-08-05 08:13:12
○NSdns5.iidns.com2016-09-11 → 2016-12-08 · 5 obs
○ 2015-11-26 01:10:00
● 2016-09-11 02:42:20
● 2016-12-08 19:10:30
○ 2018-05-29 19:22:58
○ 2026-08-05 08:13:12
● 2016-09-11 02:42:20
● 2016-12-08 19:10:30
○ 2018-05-29 19:22:58
○ 2026-08-05 08:13:12
○NSdns6.iidns.com2016-09-11 → 2016-12-08 · 5 obs
○ 2015-11-26 01:10:00
● 2016-09-11 02:42:20
● 2016-12-08 19:10:30
○ 2018-05-29 19:22:58
○ 2026-08-05 08:13:12
● 2016-09-11 02:42:20
● 2016-12-08 19:10:30
○ 2018-05-29 19:22:58
○ 2026-08-05 08:13:12
○NSns1.dnsaddress.com2015-08-07 → 2015-11-26 · 4 obs
● 2015-08-07 21:32:26
● 2015-11-26 01:10:00
○ 2016-12-08 19:10:30
○ 2026-08-05 08:13:12
● 2015-11-26 01:10:00
○ 2016-12-08 19:10:30
○ 2026-08-05 08:13:12
●NSns1.ename.net2026-04-07 → 2026-08-05 · 3 obs
○ 2018-05-29 19:22:58
● 2026-04-07 14:32:30
● 2026-08-05 08:13:12
● 2026-04-07 14:32:30
● 2026-08-05 08:13:12
●NSns2.ename.net2026-04-07 → 2026-08-05 · 3 obs
○ 2018-05-29 19:22:58
● 2026-04-07 14:32:30
● 2026-08-05 08:13:12
● 2026-04-07 14:32:30
● 2026-08-05 08:13:12
○NSns3.dns.com2018-05-29 → 2018-05-29 · 4 obs
○ 2016-12-08 19:10:30
● 2018-05-29 19:22:58
○ 2026-04-07 14:32:30
○ 2026-08-05 08:13:12
● 2018-05-29 19:22:58
○ 2026-04-07 14:32:30
○ 2026-08-05 08:13:12
○NSns4.dns.com2018-05-29 → 2018-05-29 · 4 obs
○ 2016-12-08 19:10:30
● 2018-05-29 19:22:58
○ 2026-04-07 14:32:30
○ 2026-08-05 08:13:12
● 2018-05-29 19:22:58
○ 2026-04-07 14:32:30
○ 2026-08-05 08:13:12
○A104.160.182.1322016-09-11 → 2016-12-08 · 5 obs
○ 2015-11-26 01:10:00
● 2016-09-11 02:42:20
● 2016-12-08 19:10:30
○ 2018-05-29 19:22:58
○ 2026-08-05 08:13:12
● 2016-09-11 02:42:20
● 2016-12-08 19:10:30
○ 2018-05-29 19:22:58
○ 2026-08-05 08:13:12
○A104.160.182.1342016-09-11 → 2016-09-11 · 4 obs
○ 2015-11-26 01:10:00
● 2016-09-11 02:42:20
○ 2016-12-08 19:10:30
○ 2026-08-05 08:13:12
● 2016-09-11 02:42:20
○ 2016-12-08 19:10:30
○ 2026-08-05 08:13:12
○A104.160.182.1352016-12-08 → 2016-12-08 · 4 obs
○ 2016-09-11 02:42:20
● 2016-12-08 19:10:30
○ 2018-05-29 19:22:58
○ 2026-08-05 08:13:12
● 2016-12-08 19:10:30
○ 2018-05-29 19:22:58
○ 2026-08-05 08:13:12
○A23.23.174.1322015-08-07 → 2015-11-26 · 4 obs
● 2015-08-07 21:32:26
● 2015-11-26 01:10:00
○ 2016-09-11 02:42:20
○ 2026-08-05 08:13:12
● 2015-11-26 01:10:00
○ 2016-09-11 02:42:20
○ 2026-08-05 08:13:12
🔍 DNS Trace
Analysis
Name Servers
DNS delegation for rende.com points to two name servers: ns1.ename.net and ns2.ename.net.
rende.com uses the same name servers as several other domains — among them docin.cn, zhoudingji.cn, 603323.cn and two more.
The name servers for rende.com are partially shared with other domains like 98680.com, fanhao.net and dajiahai.com
These name servers commonly appear alongside the name servers ns3.dns.com and ns4.dns.com.
Hosts that point to four IP numbers:
ns2.ename.net resolves to 1.193.216.198, 183.253.57.199, 211.99.99.52 and 240e:97d:10:1402:0:1:0:1005.
Hostnames that resolve to three IP addresses:
ns1.ename.net has IP addresses 61.158.128.31, 218.98.111.173 and 2001:df2:f080:1::8.