cmdbf.org - dns.ninja

cmdbf.org

DNSSEC⚠️ Not signed
A91.121.33.116🇫🇷 OVH91.121.0.0/16 ISP Paris, France
PTRip116.ip-91-121-33.eu
NSns1.cmdbf.org ⭐
A91.121.33.116🇫🇷 OVH91.121.0.0/16 ISP Paris, France
PTRip116.ip-91-121-33.eu
NSns2.cmdbf.org
A91.121.33.116🇫🇷 OVH91.121.0.0/16 ISP Paris, France
PTRip116.ip-91-121-33.eu
MXcmdbf.org ⭐
A91.121.33.116🇫🇷 OVH91.121.0.0/16 ISP Paris, France
PTRip116.ip-91-121-33.eu
SOAns1.cmdbf.orgoffice@cmdbf.org 2026-07-29 #1

org

DNSSEC🔒 Signed (DS record present)
NSa0.org.afilias-nst.info ⭐ ⚠️ Not in parent delegation
NSa2.org.afilias-nst.info ⚠️ Not in parent delegation
NSb0.org.afilias-nst.org
NSb2.org.afilias-nst.org
NSc0.org.afilias-nst.info ⚠️ Not in parent delegation
NSd0.org.afilias-nst.org
SOAa0.org.afilias-nst.infohostmaster@donuts.email serial=1785732190
WOT: SAFE (60/100)

MX for

cmdbf.org

Subdomains

ns2.cmdbf.org
ns1.cmdbf.org

Same first word

cmdbf.org

Similar names

bcmfd.com
bfcmd.com
mdfbc.com.cn
mcbfd.org
fdcmb.com
fmcbd.org
fcbmd.com
mfcbd.com
mdfbc.com
cmfdb.com
cbdfm.com.au
dfcbm.com
bcmfd.pl
fdmcb.com
mbcdf.de
fdmbc.com
cdbfm.com
fbcmd.org

DNS History

18 records (4 active, 14 former)

20162017201820192020202120222023202420252026NSns1.cmdbf.orgns2.cmdbf.orgns1.mynetworkdns.comns1.server40.infons1.webdns365.comns2.mynetworkdns.comns2.server40.infons2.webdns365.comns3.mynetworkdns.comns3.webdns365.comns4.mynetworkdns.comns4.webdns365.comMXcmdbf.orgA91.121.33.116104.238.133.131104.238.191.53198.58.104.17791.134.167.194
●NSns1.cmdbf.org2026-03-17 → 2026-08-03 · 3 obs
○ 2017-09-04 06:08:46
● 2026-03-17 14:09:00
● 2026-08-03 05:08:54
○NSns1.mynetworkdns.com2015-06-16 → 2015-06-16 · 3 obs
● 2015-06-16 05:58:12
○ 2015-10-24 18:05:44
○ 2026-08-03 05:08:54
○NSns1.server40.info2016-01-20 → 2016-12-29 · 5 obs
○ 2015-10-24 18:05:44
● 2016-01-20 12:32:46
● 2016-12-29 11:01:22
○ 2017-06-27 07:58:04
○ 2026-08-03 05:08:54
○NSns1.webdns365.com2015-10-24 → 2017-09-04 · 8 obs
○ 2015-06-16 05:58:12
● 2015-10-24 18:05:44
○ 2016-01-20 12:32:46
○ 2016-12-29 11:01:22
● 2017-06-27 07:58:04
● 2017-09-04 06:08:46
○ 2026-03-17 14:09:00
○ 2026-08-03 05:08:54
●NSns2.cmdbf.org2026-03-17 → 2026-08-03 · 3 obs
○ 2017-09-04 06:08:46
● 2026-03-17 14:09:00
● 2026-08-03 05:08:54
○NSns2.mynetworkdns.com2015-06-16 → 2015-06-16 · 3 obs
● 2015-06-16 05:58:12
○ 2015-10-24 18:05:44
○ 2026-08-03 05:08:54
○NSns2.server40.info2016-01-20 → 2016-12-29 · 5 obs
○ 2015-10-24 18:05:44
● 2016-01-20 12:32:46
● 2016-12-29 11:01:22
○ 2017-06-27 07:58:04
○ 2026-08-03 05:08:54
○NSns2.webdns365.com2015-10-24 → 2017-09-04 · 8 obs
○ 2015-06-16 05:58:12
● 2015-10-24 18:05:44
○ 2016-01-20 12:32:46
○ 2016-12-29 11:01:22
● 2017-06-27 07:58:04
● 2017-09-04 06:08:46
○ 2026-03-17 14:09:00
○ 2026-08-03 05:08:54
○NSns3.mynetworkdns.com2015-06-16 → 2015-06-16 · 3 obs
● 2015-06-16 05:58:12
○ 2015-10-24 18:05:44
○ 2026-08-03 05:08:54
○NSns3.webdns365.com2015-10-24 → 2017-09-04 · 8 obs
○ 2015-06-16 05:58:12
● 2015-10-24 18:05:44
○ 2016-01-20 12:32:46
○ 2016-12-29 11:01:22
● 2017-06-27 07:58:04
● 2017-09-04 06:08:46
○ 2026-03-17 14:09:00
○ 2026-08-03 05:08:54
○NSns4.mynetworkdns.com2015-06-16 → 2015-06-16 · 3 obs
● 2015-06-16 05:58:12
○ 2015-10-24 18:05:44
○ 2026-08-03 05:08:54
○NSns4.webdns365.com2015-10-24 → 2017-09-04 · 8 obs
○ 2015-06-16 05:58:12
● 2015-10-24 18:05:44
○ 2016-01-20 12:32:46
○ 2016-12-29 11:01:22
● 2017-06-27 07:58:04
● 2017-09-04 06:08:46
○ 2026-03-17 14:09:00
○ 2026-08-03 05:08:54
●MXcmdbf.org2015-06-16 → 2026-08-03 · 2 obs
● 2015-06-16 05:58:12
● 2026-08-03 05:08:54
○A104.238.133.1312015-06-16 → 2015-06-16 · 3 obs
● 2015-06-16 05:58:12
○ 2015-10-24 18:05:44
○ 2026-08-03 05:08:54
○A104.238.191.532016-01-20 → 2016-04-25 · 5 obs
○ 2015-10-24 18:05:44
● 2016-01-20 12:32:46
● 2016-04-25 18:36:54
○ 2016-06-23 13:48:08
○ 2026-08-03 05:08:54
○A198.58.104.1772015-10-24 → 2015-10-24 · 4 obs
○ 2015-06-16 05:58:12
● 2015-10-24 18:05:44
○ 2016-01-20 12:32:46
○ 2026-08-03 05:08:54
●A91.121.33.1162026-03-17 → 2026-08-03 · 3 obs
○ 2017-09-04 06:08:46
● 2026-03-17 14:09:00
● 2026-08-03 05:08:54
○A91.134.167.1942016-06-23 → 2017-09-04 · 5 obs
○ 2016-04-25 18:36:54
● 2016-06-23 13:48:08
● 2017-09-04 06:08:46
○ 2026-03-17 14:09:00
○ 2026-08-03 05:08:54

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
orgd0.org.afilias-nst.org, b0.org.afilias-nst.org, b2.org.afilias-nst.org-
cmdbf.orgns1.cmdbf.org, ns2.cmdbf.org2 records

✅ Authoritative Response

Server:91.121.33.116

NS records: ns1.cmdbf.org, ns2.cmdbf.org

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for cmdbf.org (unsigned zone)

⏱️ Timing

Total: 304ms | Queries: -

📄 Records

TypeCountSample Data
A191.121.33.116
NS2ns2.cmdbf.org, ns1.cmdbf.org
MX1cmdbf.org (pri: 0)
SOA1ns1.cmdbf.org office.cmdbf.org

📌 Glue Records Collected

Total: 2

In-bailiwick: 2 (ns1.cmdbf.org, ns2.cmdbf.org)

Analysis

Hierarchy

ns2.cmdbf.org and ns1.cmdbf.org each fall under cmdbf.org as their parent domain.

Mail Server Role

cmdbf.org handles its own mail, functioning as its own mail server.

IP Addresses

cmdbf.org resolves to just one IP address, 91.121.33.116.

ns1.cmdbf.org, monumente-funerare.org, ip116.ip-91-121-33.eu and ns2.cmdbf.org are examples of host names that share IP numbers with cmdbf.org.

Name Servers

Two name servers handle the delegation for cmdbf.org: ns1.cmdbf.org and ns2.cmdbf.org.

cmdbf.org delegates to the same name servers as other domains, monumente-funerare.org among them.

ns1.cmdbf.org directs to 91.121.33.116, as does ns2.cmdbf.org — both hostnames resolve to that one IP address.

ns1.cmdbf.org along with ns2.cmdbf.org each resolve to 91.121.33.116 IP addresses.

Mail Servers

cmdbf.org is served by just one mail server: cmdbf.org.

cmdbf.org carries a single IP number, which is 91.121.33.116.