`8033333.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}
			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}
			PTR	`ip-218-98-111-173.defastlink.net`
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}
			PTR	`ip-1-193-216-198.defastlink.net`
		A	183.253.57.199^{🇨🇳 CHINAMOBILE-CN183.253.0.0/16 CMI (Customer Route)}
			PTR	`ip-183-253-57-199.defastlink.net`
		A	211.99.99.52^{🇨🇳 DONGGUAN-1211.99.99.0/24 Proxy-registered route object}
			PTR	`ip-211-99-99-52.defastlink.net`
SOA	`ns1.ename.net`admin@ename.net serial=1751342687

`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.net`nstld@verisign-grs.com serial=1771291435

Same first word

8033333.com

Similar names

3083333.com

0338333.com

3333308.com

DNS History

21 records (2 active, 19 former)

○NSdns1.iidns.com2015-08-04 → 2017-04-03 · 4 obs

● 2015-08-04 01:09:08
● 2017-04-03 08:12:02
○ 2020-03-02 20:08:54
○ 2026-03-12 23:32:26

○NSdns2.iidns.com2015-08-04 → 2016-07-10 · 4 obs

● 2015-08-04 01:09:08
● 2016-07-10 03:03:02
○ 2017-04-03 08:12:02
○ 2026-03-12 23:32:26

○NSdns3.iidns.com2015-08-04 → 2016-07-10 · 4 obs

● 2015-08-04 01:09:08
● 2016-07-10 03:03:02
○ 2017-04-03 08:12:02
○ 2026-03-12 23:32:26

○NSdns4.iidns.com2015-08-04 → 2016-07-10 · 4 obs

● 2015-08-04 01:09:08
● 2016-07-10 03:03:02
○ 2017-04-03 08:12:02
○ 2026-03-12 23:32:26

○NSdns5.iidns.com2015-08-04 → 2016-07-10 · 4 obs

● 2015-08-04 01:09:08
● 2016-07-10 03:03:02
○ 2017-04-03 08:12:02
○ 2026-03-12 23:32:26

○NSdns6.iidns.com2015-08-04 → 2016-07-10 · 4 obs

● 2015-08-04 01:09:08
● 2016-07-10 03:03:02
○ 2017-04-03 08:12:02
○ 2026-03-12 23:32:26

●NSns1.ename.net2026-02-14 → 2026-03-12 · 3 obs

○ 2020-03-02 20:08:54
● 2026-02-14 20:57:30
● 2026-03-12 23:32:26

●NSns2.ename.net2026-02-14 → 2026-03-12 · 3 obs

○ 2020-03-02 20:08:54
● 2026-02-14 20:57:30
● 2026-03-12 23:32:26

○NSns3.dns.com2020-03-02 → 2020-03-02 · 4 obs

○ 2017-04-03 08:12:02
● 2020-03-02 20:08:54
○ 2026-02-14 20:57:30
○ 2026-03-12 23:32:26

○NSns4.dns.com2020-03-02 → 2020-03-02 · 4 obs

○ 2017-04-03 08:12:02
● 2020-03-02 20:08:54
○ 2026-02-14 20:57:30
○ 2026-03-12 23:32:26

○A198.148.92.492016-07-10 → 2016-07-10 · 4 obs

○ 2016-03-09 02:53:30
● 2016-07-10 03:03:02
○ 2017-04-03 08:12:02
○ 2026-03-12 23:32:26

○A198.148.92.502016-07-10 → 2016-07-10 · 4 obs

○ 2016-03-09 02:53:30
● 2016-07-10 03:03:02
○ 2017-04-03 08:12:02
○ 2026-03-12 23:32:26

○A198.148.92.532015-08-04 → 2026-02-15 · 3 obs

● 2015-08-04 01:09:08
● 2026-02-15 08:19:42
○ 2026-03-12 23:32:26

○A198.148.92.562015-08-04 → 2016-03-09 · 4 obs

● 2015-08-04 01:09:08
● 2016-03-09 02:53:30
○ 2016-07-10 03:03:02
○ 2026-03-12 23:32:26

○A198.148.92.572016-03-09 → 2016-03-09 · 4 obs

○ 2015-08-04 01:09:08
● 2016-03-09 02:53:30
○ 2016-07-10 03:03:02
○ 2026-03-12 23:32:26

○A198.148.92.582015-08-04 → 2016-03-09 · 4 obs

● 2015-08-04 01:09:08
● 2016-03-09 02:53:30
○ 2016-07-10 03:03:02
○ 2026-03-12 23:32:26

○A198.148.92.622015-08-04 → 2026-02-15 · 3 obs

● 2015-08-04 01:09:08
● 2026-02-15 08:19:42
○ 2026-03-12 23:32:26

○A23.234.4.1512017-04-03 → 2017-04-03 · 4 obs

○ 2016-07-10 03:03:02
● 2017-04-03 08:12:02
○ 2020-03-02 20:08:54
○ 2026-03-12 23:32:26

○A23.234.4.1532017-04-03 → 2017-04-03 · 4 obs

○ 2016-07-10 03:03:02
● 2017-04-03 08:12:02
○ 2020-03-02 20:08:54
○ 2026-03-12 23:32:26

○CNAMEfw.dnsforwardingservice.com2020-03-02 → 2026-02-15 · 4 obs

○ 2017-04-03 08:12:02
● 2020-03-02 20:08:54
● 2026-02-15 08:19:42
○ 2026-03-12 23:32:26

○CNAMEfw.ename.net2015-08-04 → 2017-04-03 · 4 obs

● 2015-08-04 01:09:08
● 2017-04-03 08:12:02
○ 2020-03-02 20:08:54
○ 2026-03-12 23:32:26

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
8033333.com	ns1.ename.net, ns2.ename.net	-

✅ Authoritative Response

Server: 183.253.57.199

NS records: ns1.ename.net, ns2.ename.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for 8033333.com (unsigned zone)

⏱️ Timing

Total: 565ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`ns1.ename.net, ns2.ename.net`
SOA	1	`ns1.ename.net admin.ename.net`

Analysis

Name Servers

8033333.com is delegated to two name servers: ns1.ename.net and ns2.ename.net.

8033333.com uses the same name server setup as other domains, including icar.com.cn, dgnet.com.cn, (0x736578)y.com.cn, 365bbc.com and fqwe.com.

8033333.com shares name servers with other domains, at least partially; for example 222727.com and 222369.com.

These name servers are commonly used alongside ns3.dns.com and ns4.dns.com.

Host names with four IP numbers:

ns2.ename.net points to 240e:97d:10:1402:0:1:0:1005, 1.193.216.198, 183.253.57.199 and 211.99.99.52.

Host names with three IP numbers:

ns1.ename.net points to 2001:df2:f080:1::8, 61.158.128.31 and 218.98.111.173.

8033333.com - robtex.com

8033333.com

com

Same first word

Similar names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

Analysis

Name Servers

`8033333.com`

`com`