sdgment.com - dns.ninja
sdgment.com
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=1781391968 | ||||||
Same first word
sdgment.com |
Similar names
DNS History
11 records (5 active, 6 former)
○NSns1.iwantmyname.net2017-08-10 → 2017-08-10 · 3 obs
○ 2026-02-16 10:05:02
○ 2026-06-13 23:34:52
●NSns1.markmonitor.com2026-02-16 → 2026-06-13 · 3 obs
● 2026-02-16 10:05:02
● 2026-06-13 23:34:52
○NSns2.iwantmyname.net2017-08-10 → 2017-08-10 · 3 obs
○ 2026-02-16 10:05:02
○ 2026-06-13 23:34:52
●NSns2.markmonitor.com2026-02-16 → 2026-06-13 · 3 obs
● 2026-02-16 10:05:02
● 2026-06-13 23:34:52
○NSns3.iwantmyname.net2017-08-10 → 2017-08-10 · 3 obs
○ 2026-02-16 10:05:02
○ 2026-06-13 23:34:52
●NSns3.markmonitor.com2026-02-16 → 2026-06-13 · 3 obs
● 2026-02-16 10:05:02
● 2026-06-13 23:34:52
○NSns4.iwantmyname.net2017-08-10 → 2017-08-10 · 3 obs
○ 2026-02-16 10:05:02
○ 2026-06-13 23:34:52
●NSns4.markmonitor.com2026-02-16 → 2026-06-13 · 3 obs
● 2026-02-16 10:05:02
● 2026-06-13 23:34:52
●A15.197.70.982026-03-13 → 2026-06-13 · 3 obs
● 2026-03-13 11:52:48
● 2026-06-13 23:34:52
○A3.33.139.322026-03-12 → 2026-03-13 · 5 obs
● 2026-03-12 17:22:20
● 2026-03-13 07:42:32
○ 2026-03-13 11:52:48
○ 2026-06-13 23:34:52
○A99.83.176.462026-02-16 → 2026-03-11 · 4 obs
● 2026-03-11 22:48:48
○ 2026-03-12 17:22:20
○ 2026-06-13 23:34:52
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | m.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| sdgment.com | ns1.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns2.markmonitor.com | 8 records |
✅ Authoritative Response
Server:149.112.160.1
NS records: ns1.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns2.markmonitor.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for sdgment.com (unsigned zone)
⏱️ Timing
Total: 322ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 15.197.70.98 |
| NS | 4 | ns1.markmonitor.com, ns2.markmonitor.com... |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | ns1.markmonitor.com hostmaster.markmonit |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns1.markmonitor.com, ns1.markmonitor.com, ns3.markmonitor.com...)
Analysis
IP Addresses
sdgment.com resolves to just one IP address, 15.197.70.98.
Two other host names, along with securax.ae, customer-data.com and twilio.help, also share IP numbers with sdgment.com.
Name Servers
sdgment.com is delegated to four name servers, ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com and ns4.markmonitor.com.
At least some of sdgment.com's name servers are shared with other domains, for example tomford.com.lb, amd.com.kw, paypalcompras.com and two more.
It is common for these name servers to be used in conjunction with the name servers ns5.markmonitor.com, ns6.markmonitor.com and ns7.markmonitor.com.
Four hostnames, each resolving to a pair of IP addresses: ns1.markmonitor.com directs to 149.112.160.1 and 2620:10a:80a8::1; ns2.markmonitor.com directs to 176.97.158.1 and 2001:67c:10b8::1; ns3.markmonitor.com directs to 149.112.161.1 and 2620:10a:80a9::1; ns4.markmonitor.com directs to 192.174.68.1 and 2001:67c:1bc::1.