idfcmf.com - robtex.com

idfcmf.com

DNSSEC⚠️ Not signed
NSns1-33.azure-dns.com ⭐ ⚠️ Not in parent delegation
A2603:1061:0:10::21🇺🇸 Microsoft2603:1000::/25 MICROSOFT
PTRns1-33.azure-dns.com
A150.171.10.33🇺🇸 Microsoft150.171.0.0/16 MICROSOFT
PTRns1-33.azure-dns.com
NSns1-34.azure-dns.com ⚠️ Not in zone NS records
A2603:1061:0:10::22🇺🇸 Microsoft2603:1000::/25 MICROSOFT
PTRns1-34.azure-dns.com
A150.171.10.34🇺🇸 Microsoft150.171.0.0/16 MICROSOFT
PTRns1-34.azure-dns.com
NSns2-33.azure-dns.net ⚠️ Not in parent delegation
A2620:1ec:8ec:10::21🇺🇸 Microsoft2620:1ec::/36 MICROSOFT
PTRns2-33.azure-dns.net
A150.171.16.33🇺🇸 Microsoft150.171.0.0/16 MICROSOFT
PTRns2-33.azure-dns.net
NSns2-34.azure-dns.net ⚠️ Not in zone NS records
A2620:1ec:8ec:10::22🇺🇸 Microsoft2620:1ec::/36 MICROSOFT
PTRns2-34.azure-dns.net
A150.171.16.34🇺🇸 Microsoft150.171.0.0/16 MICROSOFT
PTRns2-34.azure-dns.net
NSns3-33.azure-dns.org
A2a01:111:4000:10::21🇬🇧 Microsoft2a01:111:4000::/36
PTRns3-33.azure-dns.org
A13.107.222.33🇺🇸 Microsoft13.104.0.0/14 MICROSOFT
PTRns3-33.azure-dns.org
NSns4-33.azure-dns.info
A2620:1ec:bda:10::21🇺🇸 Microsoft2620:1ec::/36 MICROSOFT
PTRns4-33.azure-dns.info
A13.107.206.33🇺🇸 Microsoft13.104.0.0/14 MICROSOFT
PTRns4-33.azure-dns.info
SOAns1-33.azure-dns.comazuredns-hostmaster@microsoft.com serial=1

com

DNSSEC🔒 Signed (DS record present)
NSa.gtld-servers.net ⭐
NSb.gtld-servers.net
NSc.gtld-servers.net
NSd.gtld-servers.net
NSe.gtld-servers.net
NSf.gtld-servers.net
NSg.gtld-servers.net
NSh.gtld-servers.net
NSi.gtld-servers.net
NSj.gtld-servers.net
NSk.gtld-servers.net
NSl.gtld-servers.net
NSm.gtld-servers.net
SOAa.gtld-servers.netnstld@verisign-grs.com serial=1771291435
WOT: SAFE (88/100)

Same first word

idfcmf.com

DNS History

20 records (6 active, 14 former)

201020122014201620182020202220242026NSns1-33.azure-dns.comns1-34.azure-dns.comns2-33.azure-dns.netns2-34.azure-dns.netns3-33.azure-dns.orgns4-33.azure-dns.infodns01.idfc.comdns02.idfc.comdns03.idfc.comns5.indialinks.comns6.indialinks.comMXidfcmf-com.relay1a.spamh.comidfcmf-com.relay1b.spamh.comidfcmf-com.relay1c.spamh.comidfcmf-com.relay1g.spamh.comidfcmf-com.relay1h.spamh.comidfcmf-com.relay1i.spamh.comA202.130.41.172405:9d00:800:20:202:130:41:1740.81.71.171
○NSdns01.idfc.com2015-07-19 → 2021-07-28 · 5 obs
○ 2009-01-13 04:04:10
● 2015-07-19 11:45:00
● 2021-07-28 15:31:44
○ 2026-02-21 21:16:56
○ 2026-03-16 22:55:32
○NSdns02.idfc.com2015-07-19 → 2021-07-28 · 5 obs
○ 2009-01-13 04:04:10
● 2015-07-19 11:45:00
● 2021-07-28 15:31:44
○ 2026-02-21 21:16:56
○ 2026-03-16 22:55:32
○NSdns03.idfc.com2015-07-19 → 2017-03-06 · 5 obs
○ 2009-01-13 04:04:10
● 2015-07-19 11:45:00
● 2017-03-06 14:46:04
○ 2021-07-17 18:13:58
○ 2026-03-16 22:55:32
●NSns1-33.azure-dns.com2026-02-21 → 2026-03-16 · 6 obs
○ 2021-07-28 15:31:44
● 2026-02-21 21:16:56
● 2026-02-21 23:34:42
○ 2026-02-22 00:26:10
● 2026-02-22 04:02:46
● 2026-03-16 22:55:32
●NSns1-34.azure-dns.com2026-02-21 → 2026-03-16 · 3 obs
○ 2021-07-28 15:31:44
● 2026-02-21 21:16:56
● 2026-03-16 22:55:32
●NSns2-33.azure-dns.net2026-02-22 → 2026-03-16 · 4 obs
○ 2026-02-21 21:16:56
○ 2026-02-22 00:26:10
● 2026-02-22 04:02:46
● 2026-03-16 22:55:32
●NSns2-34.azure-dns.net2026-02-21 → 2026-03-16 · 3 obs
○ 2021-07-28 15:31:44
● 2026-02-21 21:16:56
● 2026-03-16 22:55:32
●NSns3-33.azure-dns.org2026-02-21 → 2026-03-16 · 3 obs
○ 2021-07-28 15:31:44
● 2026-02-21 21:16:56
● 2026-03-16 22:55:32
●NSns4-33.azure-dns.info2026-02-21 → 2026-03-16 · 3 obs
○ 2021-07-28 15:31:44
● 2026-02-21 21:16:56
● 2026-03-16 22:55:32
○NSns5.indialinks.com2009-01-13 → 2009-01-13 · 3 obs
● 2009-01-13 04:04:10
○ 2015-07-19 11:45:00
○ 2026-03-16 22:55:32
○NSns6.indialinks.com2009-01-13 → 2009-01-13 · 3 obs
● 2009-01-13 04:04:10
○ 2015-07-19 11:45:00
○ 2026-03-16 22:55:32
○MXidfcmf-com.relay1a.spamh.com2009-01-13 → 2009-01-13 · 3 obs
● 2009-01-13 04:04:10
○ 2015-07-19 11:45:00
○ 2026-03-16 22:55:32
○MXidfcmf-com.relay1b.spamh.com2009-01-13 → 2009-01-13 · 3 obs
● 2009-01-13 04:04:10
○ 2015-07-19 11:45:00
○ 2026-03-16 22:55:32
○MXidfcmf-com.relay1c.spamh.com2009-01-13 → 2009-01-13 · 3 obs
● 2009-01-13 04:04:10
○ 2015-07-19 11:45:00
○ 2026-03-16 22:55:32
○MXidfcmf-com.relay1g.spamh.com2015-07-19 → 2021-07-28 · 5 obs
○ 2009-01-13 04:04:10
● 2015-07-19 11:45:00
● 2021-07-28 15:31:44
○ 2026-02-21 21:16:56
○ 2026-03-16 22:55:32
○MXidfcmf-com.relay1h.spamh.com2015-07-19 → 2021-07-28 · 5 obs
○ 2009-01-13 04:04:10
● 2015-07-19 11:45:00
● 2021-07-28 15:31:44
○ 2026-02-21 21:16:56
○ 2026-03-16 22:55:32
○MXidfcmf-com.relay1i.spamh.com2015-07-19 → 2021-07-28 · 5 obs
○ 2009-01-13 04:04:10
● 2015-07-19 11:45:00
● 2021-07-28 15:31:44
○ 2026-02-21 21:16:56
○ 2026-03-16 22:55:32
○A202.130.41.172015-07-19 → 2017-03-06 · 5 obs
○ 2009-01-13 04:04:10
● 2015-07-19 11:45:00
● 2017-03-06 14:46:04
○ 2021-07-17 18:13:58
○ 2026-03-16 22:55:32
○A2405:9d00:800:20:202:130:41:172015-07-19 → 2017-03-06 · 5 obs
○ 2009-01-13 04:04:10
● 2015-07-19 11:45:00
● 2017-03-06 14:46:04
○ 2021-07-17 18:13:58
○ 2026-03-16 22:55:32
○A40.81.71.1712021-07-17 → 2021-07-28 · 5 obs
○ 2017-03-06 14:46:04
● 2021-07-17 18:13:58
● 2021-07-28 15:31:44
○ 2026-02-21 21:16:56
○ 2026-03-16 22:55:32

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
idfcmf.comns1-34.azure-dns.com, ns2-34.azure-dns.net, ns3-33.azure-dns.org, ns4-33.azure-dns.info2 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 idfcmf.com (unsigned zone)

⏱️ Timing

Total: 1243ms | Queries: -

📄 Records

TypeCountSample Data
NS4ns1-33.azure-dns.com, ns2-33.azure-dns.net...
SOA1ns1-33.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

idfcmf.com is delegated to six name servers: ns1-33.azure-dns.com, ns1-34.azure-dns.com, ns4-33.azure-dns.info, ns2-33.azure-dns.net, ns2-34.azure-dns.net and ns3-33.azure-dns.org.

idfcmf.com partially shares name servers with other domains; examples include ndurox.com, riwoods.it, 179.213.206.in-addr.arpa, 14.common.asia.azure-apihub.net and eptpartnership.com.

These name servers are often used with the name servers ns4-34.azure-dns.info and ns3-34.azure-dns.org.

Host names with two IP numbers:

ns1-33.azure-dns.com points to: 2603:1061:0:10::21 and 150.171.10.33.

ns1-34.azure-dns.com points to: 2603:1061:0:10::22 and 150.171.10.34.

ns4-33.azure-dns.info points to: 2620:1ec:bda:10::21 and 13.107.206.33.

ns2-33.azure-dns.net points to: 2620:1ec:8ec:10::21 and 150.171.16.33.

ns2-34.azure-dns.net points to: 2620:1ec:8ec:10::22 and 150.171.16.34.

ns3-33.azure-dns.org points to: 2a01:111:4000:10::21 and 13.107.222.33.