iddb.com - dns.ninja
iddb.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=1785460847 | ||||||
Same first word
Similar names
DNS History
23 records (9 active, 14 former)
○NS3dns-isi.isiport.com2007-10-24 → 2007-10-24 · 3 obs
○ 2015-08-03 16:41:58
○ 2026-07-31 01:51:02
○NS3dns-med.isiport.com2007-10-24 → 2016-04-10 · 4 obs
● 2016-04-10 07:10:50
○ 2016-04-21 10:51:20
○ 2026-07-31 01:51:02
○NSibloxgmcuste.int.thomsonreuters.com2016-04-21 → 2017-08-31 · 5 obs
● 2016-04-21 10:51:20
● 2017-08-31 05:46:52
○ 2026-05-07 12:38:26
○ 2026-07-31 01:51:02
○NSns-amers-1.thomsonreuters.net2016-04-21 → 2017-08-31 · 5 obs
● 2016-04-21 10:51:20
● 2017-08-31 05:46:52
○ 2026-05-07 12:38:26
○ 2026-07-31 01:51:02
○NSns-amers-2.thomsonreuters.net2016-04-21 → 2017-08-31 · 5 obs
● 2016-04-21 10:51:20
● 2017-08-31 05:46:52
○ 2026-05-07 12:38:26
○ 2026-07-31 01:51:02
○NSns-apac-1.thomsonreuters.net2016-04-21 → 2017-08-31 · 5 obs
● 2016-04-21 10:51:20
● 2017-08-31 05:46:52
○ 2026-05-07 12:38:26
○ 2026-07-31 01:51:02
○NSns-apac-2.thomsonreuters.net2016-04-21 → 2017-08-31 · 5 obs
● 2016-04-21 10:51:20
● 2017-08-31 05:46:52
○ 2026-05-07 12:38:26
○ 2026-07-31 01:51:02
○NSns-emea-1.thomsonreuters.net2016-04-21 → 2017-08-31 · 5 obs
● 2016-04-21 10:51:20
● 2017-08-31 05:46:52
○ 2026-05-07 12:38:26
○ 2026-07-31 01:51:02
○NSns-emea-2.thomsonreuters.net2016-04-21 → 2017-08-31 · 5 obs
● 2016-04-21 10:51:20
● 2017-08-31 05:46:52
○ 2026-05-07 12:38:26
○ 2026-07-31 01:51:02
●NSns1.markmonitor.com2026-05-07 → 2026-07-31 · 3 obs
● 2026-05-07 12:38:26
● 2026-07-31 01:51:02
●NSns2.markmonitor.com2026-05-07 → 2026-07-31 · 3 obs
● 2026-05-07 12:38:26
● 2026-07-31 01:51:02
○NSns21.westgroup.net2015-08-03 → 2016-04-10 · 5 obs
● 2015-08-03 16:41:58
● 2016-04-10 07:10:50
○ 2016-04-21 10:51:20
○ 2026-07-31 01:51:02
○NSns22.westgroup.net2015-08-03 → 2016-04-10 · 5 obs
● 2015-08-03 16:41:58
● 2016-04-10 07:10:50
○ 2016-04-21 10:51:20
○ 2026-07-31 01:51:02
○NSns23.westgroup.net2015-08-03 → 2016-04-10 · 5 obs
● 2015-08-03 16:41:58
● 2016-04-10 07:10:50
○ 2016-04-21 10:51:20
○ 2026-07-31 01:51:02
●NSns3.markmonitor.com2026-05-07 → 2026-07-31 · 3 obs
● 2026-05-07 12:38:26
● 2026-07-31 01:51:02
●NSns4.markmonitor.com2026-05-07 → 2026-07-31 · 3 obs
● 2026-05-07 12:38:26
● 2026-07-31 01:51:02
●NSns5.markmonitor.com2026-05-07 → 2026-07-31 · 3 obs
● 2026-05-07 12:38:26
● 2026-07-31 01:51:02
●NSns6.markmonitor.com2026-05-07 → 2026-07-31 · 3 obs
● 2026-05-07 12:38:26
● 2026-07-31 01:51:02
●NSns7.markmonitor.com2026-05-07 → 2026-07-31 · 3 obs
● 2026-05-07 12:38:26
● 2026-07-31 01:51:02
●MXmail27.messagelabs.com2007-10-24 → 2026-07-31 · 2 obs
● 2026-07-31 01:51:02
●MXmail32.messagelabs.com2007-10-24 → 2026-07-31 · 2 obs
● 2026-07-31 01:51:02
○A170.107.172.942015-08-03 → 2016-02-14 · 5 obs
● 2015-08-03 16:41:58
● 2016-02-14 22:42:14
○ 2016-04-10 07:10:50
○ 2026-07-31 01:51:02
○A170.107.183.232007-10-24 → 2007-10-24 · 3 obs
○ 2015-08-03 16:41:58
○ 2026-07-31 01:51:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | b.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, e.gtld-servers.net... | - |
| iddb.com | ns1.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com... | 14 records |
✅ Authoritative Response
Server:149.112.160.2
NS records: ns1.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com, ns6.markmonitor.com, ns7.markmonitor.com, ns2.markmonitor.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for iddb.com (unsigned zone)
⏱️ Timing
Total: 570ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 7 | ns1.markmonitor.com, ns2.markmonitor.com... |
| MX | 2 | mail32.messagelabs.com (pri: 10), mail27.messagelabs.com (pri: 20) |
| SOA | 1 | ns1.markmonitor.com hostmaster.markmonit |
📌 Glue Records Collected
Total: 14
Out-of-bailiwick: 14 (ns1.markmonitor.com, ns1.markmonitor.com, ns3.markmonitor.com...)
Analysis
Name Servers
iddb.com carries NS records listing 7 name servers — ns1.markmonitor.com, ns2.markmonitor.com, ns3.markmonitor.com and 4 others.
There is at least partial name server overlap between iddb.com and other domains — holidayinnselectboston.com, hiltoncopacabana.com.br, ignidex.com and two more among them.
These name servers tend to appear in combination with the name servers ns4.markmonitor.com, ns5.markmonitor.com, ns6.markmonitor.com and ns7.markmonitor.com.
Hosts with two IP numbers each:
The A records for ns1.markmonitor.com return 149.112.160.1 and 2620:10a:80a8::1.
The A records for ns2.markmonitor.com return 176.97.158.1 and 2001:67c:10b8::1.
The A records for ns3.markmonitor.com return 149.112.161.1 and 2620:10a:80a9::1.
The A records for ns4.markmonitor.com return 192.174.68.1 and 2001:67c:1bc::1.
The A records for ns5.markmonitor.com return 149.112.160.2 and 2620:10a:80a8::2.
The A records for ns6.markmonitor.com return 176.97.158.3 and 2001:67c:10b8::3.
The A records for ns7.markmonitor.com return 149.112.161.2 and 2620:10a:80a9::2.
Mail Servers
The MX records for iddb.com point to two mail servers: mail27.messagelabs.com and mail32.messagelabs.com.
iddb.com has the same mail server arrangement as a number of other domains, for example wedeco-visa.com, current-drugs.com, current-patents.com and two more.
iddb.com shares at least some of its mail servers with other domains — for example eveningtelegraph.com, lovell-homes.net, ri-pestcontrol.com and two more.
These mail servers are routinely seen in conjunction with the mail servers mail1.messagelabs.com and mail2.cableinet.net.
Hosts that resolve to one IP address:
mail32.messagelabs.com resolves to the IP address 85.158.139.211.