333sf.com - robtex.com
333sf.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 198.148.84.119🇺🇸 SHARKTECH-1198.148.84.0/24 | ||||||
| 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 | ||||||
| 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=1751342647 | ||||||
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=1775121332 | ||||||
Same first word
Similar names
DNS History
15 records (3 active, 12 former)
○NSdns1.iidns.com2016-07-04 → 2017-02-20 · 5 obs
○ 2016-02-03 06:22:50
● 2016-07-04 16:52:56
● 2017-02-20 09:18:38
○ 2026-03-30 01:06:18
○ 2026-04-02 09:28:26
● 2016-07-04 16:52:56
● 2017-02-20 09:18:38
○ 2026-03-30 01:06:18
○ 2026-04-02 09:28:26
○NSdns2.iidns.com2016-07-04 → 2017-02-20 · 5 obs
○ 2016-02-03 06:22:50
● 2016-07-04 16:52:56
● 2017-02-20 09:18:38
○ 2026-03-30 01:06:18
○ 2026-04-02 09:28:26
● 2016-07-04 16:52:56
● 2017-02-20 09:18:38
○ 2026-03-30 01:06:18
○ 2026-04-02 09:28:26
○NSdns3.iidns.com2016-07-04 → 2017-02-20 · 5 obs
○ 2016-02-03 06:22:50
● 2016-07-04 16:52:56
● 2017-02-20 09:18:38
○ 2026-03-30 01:06:18
○ 2026-04-02 09:28:26
● 2016-07-04 16:52:56
● 2017-02-20 09:18:38
○ 2026-03-30 01:06:18
○ 2026-04-02 09:28:26
○NSdns4.iidns.com2016-07-04 → 2017-02-20 · 5 obs
○ 2016-02-03 06:22:50
● 2016-07-04 16:52:56
● 2017-02-20 09:18:38
○ 2026-03-30 01:06:18
○ 2026-04-02 09:28:26
● 2016-07-04 16:52:56
● 2017-02-20 09:18:38
○ 2026-03-30 01:06:18
○ 2026-04-02 09:28:26
○NSdns5.iidns.com2016-07-04 → 2017-02-20 · 5 obs
○ 2016-02-03 06:22:50
● 2016-07-04 16:52:56
● 2017-02-20 09:18:38
○ 2026-03-30 01:06:18
○ 2026-04-02 09:28:26
● 2016-07-04 16:52:56
● 2017-02-20 09:18:38
○ 2026-03-30 01:06:18
○ 2026-04-02 09:28:26
○NSdns6.iidns.com2016-07-04 → 2017-02-20 · 5 obs
○ 2016-02-03 06:22:50
● 2016-07-04 16:52:56
● 2017-02-20 09:18:38
○ 2026-03-30 01:06:18
○ 2026-04-02 09:28:26
● 2016-07-04 16:52:56
● 2017-02-20 09:18:38
○ 2026-03-30 01:06:18
○ 2026-04-02 09:28:26
●NSns1.ename.net2026-03-30 → 2026-04-02 · 3 obs
○ 2017-02-20 09:18:38
● 2026-03-30 01:06:18
● 2026-04-02 09:28:26
● 2026-03-30 01:06:18
● 2026-04-02 09:28:26
○NSns1.zndns.com2015-05-24 → 2016-02-03 · 5 obs
○ 2008-03-09 10:17:44
● 2015-05-24 21:42:16
● 2016-02-03 06:22:50
○ 2016-07-04 16:52:56
○ 2026-04-02 09:28:26
● 2015-05-24 21:42:16
● 2016-02-03 06:22:50
○ 2016-07-04 16:52:56
○ 2026-04-02 09:28:26
●NSns2.ename.net2026-03-30 → 2026-04-02 · 3 obs
○ 2017-02-20 09:18:38
● 2026-03-30 01:06:18
● 2026-04-02 09:28:26
● 2026-03-30 01:06:18
● 2026-04-02 09:28:26
○NSns2.xinnet.cn2008-03-09 → 2008-03-09 · 3 obs
● 2008-03-09 10:17:44
○ 2015-05-24 21:42:16
○ 2026-04-02 09:28:26
○ 2015-05-24 21:42:16
○ 2026-04-02 09:28:26
○NSns2.xinnetdns.com2008-03-09 → 2008-03-09 · 3 obs
● 2008-03-09 10:17:44
○ 2015-05-24 21:42:16
○ 2026-04-02 09:28:26
○ 2015-05-24 21:42:16
○ 2026-04-02 09:28:26
○NSns2.zndns.com2015-05-24 → 2015-11-01 · 5 obs
○ 2008-03-09 10:17:44
● 2015-05-24 21:42:16
● 2015-11-01 11:33:52
○ 2016-07-04 16:52:56
○ 2026-04-02 09:28:26
● 2015-05-24 21:42:16
● 2015-11-01 11:33:52
○ 2016-07-04 16:52:56
○ 2026-04-02 09:28:26
○NSns3.zndns.com2015-05-24 → 2015-11-01 · 5 obs
○ 2008-03-09 10:17:44
● 2015-05-24 21:42:16
● 2015-11-01 11:33:52
○ 2016-07-04 16:52:56
○ 2026-04-02 09:28:26
● 2015-05-24 21:42:16
● 2015-11-01 11:33:52
○ 2016-07-04 16:52:56
○ 2026-04-02 09:28:26
○A121.11.85.462008-03-09 → 2008-03-09 · 3 obs
● 2008-03-09 10:17:44
○ 2015-05-24 21:42:16
○ 2026-04-02 09:28:26
○ 2015-05-24 21:42:16
○ 2026-04-02 09:28:26
●A198.148.84.1192015-05-24 → 2026-04-02 · 3 obs
○ 2008-03-09 10:17:44
● 2015-05-24 21:42:16
● 2026-04-02 09:28:26
● 2015-05-24 21:42:16
● 2026-04-02 09:28:26
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| 333sf.com | ns1.ename.net, ns2.ename.net | - |
✅ Authoritative Response
Server:218.98.111.173
NS records: ns1.ename.net, ns2.ename.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for 333sf.com (unsigned zone)
⏱️ Timing
Total: 2978ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 198.148.84.119 |
| NS | 2 | ns1.ename.net, ns2.ename.net |
| SOA | 1 | ns1.ename.net admin.ename.net |
Analysis
IP Addresses
333sf.com resolves to a single IP: 198.148.84.119.
Name Servers
333sf.com has two name servers: ns1.ename.net and ns2.ename.net.
333sf.com shares the same name server setup as other domains, for example chuiai.com, 55638.com, 9fd.com, qjmc.com and tuiju.cn.
333sf.com shares some name servers with other domains, for example peiwa.com, ojir.com, poci.net, 4963.cn and 8820game.com.
These name servers are commonly used together with ns3.dns.com and ns4.dns.com.
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. Three IP numbers: ns1.ename.net points to 2001:df2:f080:1::8, 61.158.128.31 and 218.98.111.173.