idfc.com - dns.ninja
idfc.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=1782509465 | ||||||
Same first word
idfc.in |
idfc.biz |
idfc.fr |
idfc.org |
idfc.co.in |
idfc.com.mx |
idfc.mobi |
idfc.gov |
idfc.com |
idfc.ru |
idfc.info |
idfc.de |
idfc.eu |
idfc.net |
idfc.mx |
idfc.us |
Similar names
DNS History
16 records (6 active, 10 former)
○NSdns01.idfc.com2015-07-23 → 2017-10-05 · 4 obs
● 2017-10-05 04:10:48
○ 2026-03-06 23:02:34
○ 2026-06-26 21:40:26
○NSdns02.idfc.com2015-07-23 → 2017-10-05 · 4 obs
● 2017-10-05 04:10:48
○ 2026-03-06 23:02:34
○ 2026-06-26 21:40:26
○NSdns03.idfc.com2015-07-23 → 2017-10-05 · 4 obs
● 2017-10-05 04:10:48
○ 2026-03-06 23:02:34
○ 2026-06-26 21:40:26
●NSns1-34.azure-dns.com2026-03-06 → 2026-06-26 · 3 obs
● 2026-03-06 23:02:34
● 2026-06-26 21:40:26
●NSns2-34.azure-dns.net2026-03-06 → 2026-06-26 · 3 obs
● 2026-03-06 23:02:34
● 2026-06-26 21:40:26
●NSns3-33.azure-dns.org2026-03-06 → 2026-06-26 · 3 obs
● 2026-03-06 23:02:34
● 2026-06-26 21:40:26
●NSns3-34.azure-dns.org2026-03-06 → 2026-06-26 · 16 obs
● 2026-03-06 23:02:34
○ 2026-03-10 04:01:54
○ 2026-03-26 11:58:32
● 2026-03-26 20:09:32
○ 2026-03-26 20:51:32
○ 2026-03-27 04:57:10
● 2026-03-30 11:23:58
○ 2026-04-01 11:28:42
● 2026-04-03 11:21:38
○ 2026-04-05 11:20:02
● 2026-04-06 21:06:50
● 2026-04-22 12:56:28
○ 2026-04-24 13:29:14
● 2026-04-26 13:54:40
● 2026-06-26 21:40:26
●NSns4-33.azure-dns.info2026-03-06 → 2026-06-26 · 3 obs
● 2026-03-06 23:02:34
● 2026-06-26 21:40:26
●NSns4-34.azure-dns.info2026-03-06 → 2026-06-26 · 16 obs
● 2026-03-06 23:02:34
○ 2026-03-10 04:01:54
○ 2026-03-26 11:58:32
● 2026-03-26 20:09:32
○ 2026-03-26 20:51:32
○ 2026-03-27 04:57:10
● 2026-03-30 11:23:58
○ 2026-04-01 11:28:42
● 2026-04-03 11:21:38
○ 2026-04-05 11:20:02
● 2026-04-06 21:06:50
● 2026-04-22 12:56:28
○ 2026-04-24 13:29:14
● 2026-04-26 13:54:40
● 2026-06-26 21:40:26
○MXenvmx.etransmail.com2026-03-06 → 2026-04-26 · 14 obs
● 2026-03-06 23:02:34
○ 2026-03-10 04:01:54
● 2026-03-26 11:58:32
○ 2026-03-26 20:09:32
○ 2026-03-30 11:23:58
● 2026-04-01 11:28:42
○ 2026-04-03 11:21:38
● 2026-04-05 11:20:02
● 2026-04-17 12:11:46
○ 2026-04-19 12:14:20
● 2026-04-22 12:56:28
● 2026-04-26 13:54:40
○ 2026-06-26 21:40:26
○MXidfc-com.mail.protection.outlook.com2026-03-06 → 2026-04-26 · 14 obs
● 2026-03-06 23:02:34
○ 2026-03-10 04:01:54
● 2026-03-26 11:58:32
○ 2026-03-26 20:09:32
○ 2026-03-30 11:23:58
● 2026-04-01 11:28:42
○ 2026-04-03 11:21:38
● 2026-04-05 11:20:02
● 2026-04-17 12:11:46
○ 2026-04-19 12:14:20
● 2026-04-22 12:56:28
● 2026-04-26 13:54:40
○ 2026-06-26 21:40:26
○MXidfc-com.relay1g.spamh.com2015-07-23 → 2017-10-05 · 4 obs
● 2017-10-05 04:10:48
○ 2026-03-06 23:02:34
○ 2026-06-26 21:40:26
○MXidfc-com.relay1h.spamh.com2015-07-23 → 2017-10-05 · 4 obs
● 2017-10-05 04:10:48
○ 2026-03-06 23:02:34
○ 2026-06-26 21:40:26
○MXidfc-com.relay1i.spamh.com2015-07-23 → 2017-10-05 · 4 obs
● 2017-10-05 04:10:48
○ 2026-03-06 23:02:34
○ 2026-06-26 21:40:26
○A202.130.41.132015-07-23 → 2017-10-05 · 4 obs
● 2017-10-05 04:10:48
○ 2026-03-06 23:02:34
○ 2026-06-26 21:40:26
○A2405:9d00:800:20:202:130:41:132015-07-23 → 2017-10-05 · 4 obs
● 2017-10-05 04:10:48
○ 2026-03-06 23:02:34
○ 2026-06-26 21:40: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... | - |
| idfc.com | ns1-34.azure-dns.com, ns2-34.azure-dns.net, ns3-33.azure-dns.org, ns4-33.azure-dns.info | 2 records |
✅ Authoritative Response
Server:13.107.206.33
NS records: ns1-34.azure-dns.com, ns2-34.azure-dns.net, ns3-33.azure-dns.org, ns4-33.azure-dns.info
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for idfc.com (unsigned zone)
⏱️ Timing
Total: 493ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns1-34.azure-dns.com, ns2-34.azure-dns.net... |
| MX | 2 | idfc-com.mail.protection.outlook.com (pr, envmx.etransmail.com (pri: 10) |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | ns1-34.azure-dns.com azuredns-hostmaster |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1-34.azure-dns.com, ns1-34.azure-dns.com)
Analysis
Name Servers
idfc.com has 6 name servers — ns1-34.azure-dns.com, ns4-33.azure-dns.info, ns4-34.azure-dns.info and 3 others.
idfc.com has at least partial name server overlap with other domains, such as vejlekommunesmusikskole.dk, sportball.us, kaylumah.nl and two others.
The name servers ns2-34.azure-dns.net, ns3-34.azure-dns.org, ns1-33.azure-dns.com and two others are commonly seen in use alongside these name servers.
Host names that have two IP addresses:
ns1-34.azure-dns.com resolves to 150.171.10.34 and 2603:1061:0:10::22.
ns4-33.azure-dns.info resolves to 13.107.206.33 and 2620:1ec:bda:10::21.
ns4-34.azure-dns.info resolves to 13.107.206.34 and 2620:1ec:bda:10::22.
ns2-34.azure-dns.net resolves to 150.171.16.34 and 2620:1ec:8ec:10::22.
ns3-33.azure-dns.org resolves to 13.107.222.33 and 2a01:111:4000:10::21.
ns3-34.azure-dns.org resolves to 13.107.222.34 and 2a01:111:4000:10::22.