shipdata.com - dns.ninja
shipdata.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.ename.net ⭐ | ||||||
| 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 | ||||||
| A | 218.98.111.173🇩🇪 HKCICL-AS-AP218.98.111.0/24 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED | ||||||
| NS | ns2.ename.net | ||||||
| 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 Proxy-registered route object | ||||||
| SOA | ns1.ename.netadmin@ename.net serial=1775870889 | ||||||
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=1783664717 | ||||||
Subdomains
www.shipdata.com |
Same first word
Similar names
dashapit.com |
dataship.com |
stihpada.ac.id |
hispadat.com |
adaptish.com |
padsthai.com |
datahips.com |
dataship.netlify.app |
dataship.de |
dataship.org |
dataship.com.br |
DNS History
14 records (2 active, 12 former)
○NSns1.aylan.net2015-06-25 → 2017-06-10 · 4 obs
● 2015-06-25 11:00:22
● 2017-06-10 16:07:36
○ 2026-02-15 23:10:08
○ 2026-07-10 06:41:40
● 2017-06-10 16:07:36
○ 2026-02-15 23:10:08
○ 2026-07-10 06:41:40
●NSns1.ename.net2026-04-13 → 2026-07-10 · 3 obs
○ 2026-03-26 20:44:16
● 2026-04-13 18:05:56
● 2026-07-10 06:41:40
● 2026-04-13 18:05:56
● 2026-07-10 06:41:40
○NSns1.namebrightdns.com2026-02-15 → 2026-03-26 · 5 obs
○ 2017-06-10 16:07:36
● 2026-02-15 23:10:08
● 2026-03-26 20:44:16
○ 2026-04-13 18:05:56
○ 2026-07-10 06:41:40
● 2026-02-15 23:10:08
● 2026-03-26 20:44:16
○ 2026-04-13 18:05:56
○ 2026-07-10 06:41:40
○NSns2.aylan.net2015-06-25 → 2017-06-10 · 4 obs
● 2015-06-25 11:00:22
● 2017-06-10 16:07:36
○ 2026-02-15 23:10:08
○ 2026-07-10 06:41:40
● 2017-06-10 16:07:36
○ 2026-02-15 23:10:08
○ 2026-07-10 06:41:40
●NSns2.ename.net2026-04-13 → 2026-07-10 · 3 obs
○ 2026-03-26 20:44:16
● 2026-04-13 18:05:56
● 2026-07-10 06:41:40
● 2026-04-13 18:05:56
● 2026-07-10 06:41:40
○NSns2.namebrightdns.com2026-02-15 → 2026-03-26 · 5 obs
○ 2017-06-10 16:07:36
● 2026-02-15 23:10:08
● 2026-03-26 20:44:16
○ 2026-04-13 18:05:56
○ 2026-07-10 06:41:40
● 2026-02-15 23:10:08
● 2026-03-26 20:44:16
○ 2026-04-13 18:05:56
○ 2026-07-10 06:41:40
○MXmail.shipdata.com2015-06-25 → 2017-06-10 · 4 obs
● 2015-06-25 11:00:22
● 2017-06-10 16:07:36
○ 2026-02-15 23:10:08
○ 2026-07-10 06:41:40
● 2017-06-10 16:07:36
○ 2026-02-15 23:10:08
○ 2026-07-10 06:41:40
○MXmail1.namebrightmail.com2026-02-15 → 2026-03-26 · 5 obs
○ 2017-06-10 16:07:36
● 2026-02-15 23:10:08
● 2026-03-26 20:44:16
○ 2026-04-13 18:05:56
○ 2026-07-10 06:41:40
● 2026-02-15 23:10:08
● 2026-03-26 20:44:16
○ 2026-04-13 18:05:56
○ 2026-07-10 06:41:40
○MXmail2.namebrightmail.com2026-02-15 → 2026-03-26 · 5 obs
○ 2017-06-10 16:07:36
● 2026-02-15 23:10:08
● 2026-03-26 20:44:16
○ 2026-04-13 18:05:56
○ 2026-07-10 06:41:40
● 2026-02-15 23:10:08
● 2026-03-26 20:44:16
○ 2026-04-13 18:05:56
○ 2026-07-10 06:41:40
○A188.125.171.982015-06-25 → 2017-06-10 · 4 obs
● 2015-06-25 11:00:22
● 2017-06-10 16:07:36
○ 2026-02-15 23:10:08
○ 2026-07-10 06:41:40
● 2017-06-10 16:07:36
○ 2026-02-15 23:10:08
○ 2026-07-10 06:41:40
○A2600:1f18:4ae:c607:d1d9:565f:b122:bfdb2026-02-15 → 2026-03-26 · 5 obs
○ 2017-06-10 16:07:36
● 2026-02-15 23:10:08
● 2026-03-26 20:44:16
○ 2026-04-13 18:05:56
○ 2026-07-10 06:41:40
● 2026-02-15 23:10:08
● 2026-03-26 20:44:16
○ 2026-04-13 18:05:56
○ 2026-07-10 06:41:40
○A2600:1f18:4ae:c608:83f8:2f9c:4a61:7b6a2026-02-15 → 2026-03-26 · 5 obs
○ 2017-06-10 16:07:36
● 2026-02-15 23:10:08
● 2026-03-26 20:44:16
○ 2026-04-13 18:05:56
○ 2026-07-10 06:41:40
● 2026-02-15 23:10:08
● 2026-03-26 20:44:16
○ 2026-04-13 18:05:56
○ 2026-07-10 06:41:40
○A52.44.244.982026-02-15 → 2026-03-26 · 5 obs
○ 2017-06-10 16:07:36
● 2026-02-15 23:10:08
● 2026-03-26 20:44:16
○ 2026-04-13 18:05:56
○ 2026-07-10 06:41:40
● 2026-02-15 23:10:08
● 2026-03-26 20:44:16
○ 2026-04-13 18:05:56
○ 2026-07-10 06:41:40
○A54.165.131.1832026-02-15 → 2026-03-26 · 5 obs
○ 2017-06-10 16:07:36
● 2026-02-15 23:10:08
● 2026-03-26 20:44:16
○ 2026-04-13 18:05:56
○ 2026-07-10 06:41:40
● 2026-02-15 23:10:08
● 2026-03-26 20:44:16
○ 2026-04-13 18:05:56
○ 2026-07-10 06:41:40
🔍 DNS Trace
Analysis
Hierarchy
shipdata.com is a parent domain of www.shipdata.com.
Name Servers
Two name servers handle the delegation for shipdata.com: ns1.ename.net and ns2.ename.net.
shipdata.com has the same name server delegation as a number of other domains, such as 1032.com.cn, jzznet.cn, yaosa.com and two more.
There is an overlap in name servers between shipdata.com and other domains, for example rucou.com, wzl.com and heimen.com
These name servers are frequently paired with the name servers ns3.dns.com and ns4.dns.com.
Hosts pointing to four IP addresses:
ns2.ename.net points to 1.193.216.198, 183.253.57.199, 211.99.99.52 and 240e:97d:10:1402:0:1:0:1005.
Hosts with three IP address records:
The hostname ns1.ename.net points to 61.158.128.31, 218.98.111.173 and 2001:df2:f080:1::8.