sgddlaw.com - robtex.com
sgddlaw.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 107.163.47.76🇺🇸 AS395776107.163.47.0/24 SKBroadband customer route | ||||||
| NS | ns1.dns.com ⭐ | ||||||
| A | 2001:df2:f080:2::1:1🇭🇰 HKCICL-AS-AP2001:df2:f080::/48 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED | ||||||
| A | 154.23.191.128🇺🇸 HKCICL-AS-AP154.23.191.0/24 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED | ||||||
| A | 154.86.21.128🇭🇰 HKCICL-AS-AP154.86.21.0/24 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED | ||||||
| NS | ns2.dns.com | ||||||
| A | 2001:df2:f080:2::1:2🇭🇰 HKCICL-AS-AP2001:df2:f080::/48 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED | ||||||
| A | 154.23.191.129🇺🇸 HKCICL-AS-AP154.23.191.0/24 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED | ||||||
| A | 154.86.21.129🇭🇰 HKCICL-AS-AP154.86.21.0/24 HONG KONG COMMUNICATIONS INTERNATIONAL CO.,LIMITED | ||||||
| SOA | ns1.dns.comadmin@dns.com serial=1765844197 | ||||||
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=1782178410 | ||||||
rank #398546 in the tld
Same first word
sgddlaw.com |
DNS History
17 records (3 active, 14 former)
○NSdns1.name-services.com2017-09-08 → 2017-09-08 · 3 obs
● 2017-09-08 02:55:14
○ 2026-05-22 07:14:10
○ 2026-06-23 02:01:52
○ 2026-05-22 07:14:10
○ 2026-06-23 02:01:52
○NSdns2.name-services.com2017-09-08 → 2017-09-08 · 3 obs
● 2017-09-08 02:55:14
○ 2026-05-22 07:14:10
○ 2026-06-23 02:01:52
○ 2026-05-22 07:14:10
○ 2026-06-23 02:01:52
○NSdns3.name-services.com2017-09-08 → 2017-09-08 · 3 obs
● 2017-09-08 02:55:14
○ 2026-05-22 07:14:10
○ 2026-06-23 02:01:52
○ 2026-05-22 07:14:10
○ 2026-06-23 02:01:52
○NSdns4.name-services.com2017-09-08 → 2017-09-08 · 3 obs
● 2017-09-08 02:55:14
○ 2026-05-22 07:14:10
○ 2026-06-23 02:01:52
○ 2026-05-22 07:14:10
○ 2026-06-23 02:01:52
○NSdns5.name-services.com2017-09-08 → 2017-09-08 · 3 obs
● 2017-09-08 02:55:14
○ 2026-05-22 07:14:10
○ 2026-06-23 02:01:52
○ 2026-05-22 07:14:10
○ 2026-06-23 02:01:52
●NSns1.dns.com2026-05-22 → 2026-06-23 · 3 obs
○ 2017-09-08 02:55:14
● 2026-05-22 07:14:10
● 2026-06-23 02:01:52
● 2026-05-22 07:14:10
● 2026-06-23 02:01:52
●NSns2.dns.com2026-05-22 → 2026-06-23 · 3 obs
○ 2017-09-08 02:55:14
● 2026-05-22 07:14:10
● 2026-06-23 02:01:52
● 2026-05-22 07:14:10
● 2026-06-23 02:01:52
○MXalt1.aspmx.l.google.com2017-09-08 → 2017-09-08 · 3 obs
● 2017-09-08 02:55:14
○ 2026-05-22 07:14:10
○ 2026-06-23 02:01:52
○ 2026-05-22 07:14:10
○ 2026-06-23 02:01:52
○MXalt2.aspmx.l.google.com2017-09-08 → 2017-09-08 · 3 obs
● 2017-09-08 02:55:14
○ 2026-05-22 07:14:10
○ 2026-06-23 02:01:52
○ 2026-05-22 07:14:10
○ 2026-06-23 02:01:52
○MXaspmx.l.google.com2017-09-08 → 2017-09-08 · 3 obs
● 2017-09-08 02:55:14
○ 2026-05-22 07:14:10
○ 2026-06-23 02:01:52
○ 2026-05-22 07:14:10
○ 2026-06-23 02:01:52
○MXaspmx2.googlemail.com2017-09-08 → 2017-09-08 · 3 obs
● 2017-09-08 02:55:14
○ 2026-05-22 07:14:10
○ 2026-06-23 02:01:52
○ 2026-05-22 07:14:10
○ 2026-06-23 02:01:52
○MXaspmx3.googlemail.com2017-09-08 → 2017-09-08 · 3 obs
● 2017-09-08 02:55:14
○ 2026-05-22 07:14:10
○ 2026-06-23 02:01:52
○ 2026-05-22 07:14:10
○ 2026-06-23 02:01:52
●A107.163.47.762026-05-22 → 2026-06-23 · 3 obs
○ 2017-09-08 02:55:14
● 2026-05-22 07:14:10
● 2026-06-23 02:01:52
● 2026-05-22 07:14:10
● 2026-06-23 02:01:52
○A216.239.32.212017-09-08 → 2017-09-08 · 3 obs
● 2017-09-08 02:55:14
○ 2026-05-22 07:14:10
○ 2026-06-23 02:01:52
○ 2026-05-22 07:14:10
○ 2026-06-23 02:01:52
○A216.239.34.212017-09-08 → 2017-09-08 · 3 obs
● 2017-09-08 02:55:14
○ 2026-05-22 07:14:10
○ 2026-06-23 02:01:52
○ 2026-05-22 07:14:10
○ 2026-06-23 02:01:52
○A216.239.36.212017-09-08 → 2017-09-08 · 3 obs
● 2017-09-08 02:55:14
○ 2026-05-22 07:14:10
○ 2026-06-23 02:01:52
○ 2026-05-22 07:14:10
○ 2026-06-23 02:01:52
○A216.239.38.212017-09-08 → 2017-09-08 · 3 obs
● 2017-09-08 02:55:14
○ 2026-05-22 07:14:10
○ 2026-06-23 02:01:52
○ 2026-05-22 07:14:10
○ 2026-06-23 02:01:52
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| sgddlaw.com | ns1.dns.com, ns2.dns.com | 6 records |
✅ Authoritative Response
Server:154.23.191.128
NS records: ns1.dns.com, ns2.dns.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for sgddlaw.com (unsigned zone)
⏱️ Timing
Total: 263ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 107.163.47.76 |
| NS | 2 | ns1.dns.com, ns2.dns.com |
| SOA | 1 | ns1.dns.com admin.dns.com |
📌 Glue Records Collected
Total: 6
Out-of-bailiwick: 6 (ns1.dns.com, ns1.dns.com, ns1.dns.com...)
Analysis
IP Addresses
sgddlaw.com resolves to one IP address: 107.163.47.76.
veskychina.com, uni-texasedu.com, cspenshaji.com and two other host names share IP numbers with sgddlaw.com.
Name Servers
DNS delegation for sgddlaw.com points to two name servers: ns1.dns.com and ns2.dns.com.
sgddlaw.com uses the same name servers as several other domains — among them 2289.com, mkwhw.com, jy70.net and two more.
ns1.dns.com and ns2.dns.com each resolve to three IP addresses. ns1.dns.com resolves to 154.23.191.128, 154.86.21.128 and 2001:df2:f080:2::1:1. ns2.dns.com resolves to 154.23.191.129, 154.86.21.129 and 2001:df2:f080:2::1:2.