bmfc.com - dns.ninja
bmfc.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=1786954794 | ||||||
Previously MX for
bmfc.com |
Same first word
bmfc.eu |
bmfc.com.au |
bmfc.club |
bmfc.fr |
bmfc.org |
bmfc.nl |
bmfc.co |
bmfc.lv |
bmfc.asia |
bmfc.com |
bmfc.de |
bmfc.ru |
bmfc.net |
bmfc.ca |
Similar names
DNS History
25 records (11 active, 14 former)
○NSns1.dataplugs.com2015-11-25 → 2016-07-19 · 5 obs
● 2015-11-25 00:11:24
● 2016-07-19 16:47:56
○ 2017-07-07 09:41:42
○ 2026-08-17 08:40:08
○NSns1.ev1servers.net2007-10-27 → 2007-10-27 · 3 obs
○ 2015-07-21 19:02:06
○ 2026-08-17 08:40:08
●NSns1.name.com2026-03-27 → 2026-08-17 · 3 obs
● 2026-03-27 05:50:22
● 2026-08-17 08:40:08
●NSns1fkl.name.com2017-07-07 → 2026-08-17 · 3 obs
● 2017-07-07 09:41:42
● 2026-08-17 08:40:08
○NSns2.dataplugs.com2015-11-25 → 2016-07-19 · 5 obs
● 2015-11-25 00:11:24
● 2016-07-19 16:47:56
○ 2017-07-07 09:41:42
○ 2026-08-17 08:40:08
○NSns2.ev1servers.net2007-10-27 → 2007-10-27 · 3 obs
○ 2015-07-21 19:02:06
○ 2026-08-17 08:40:08
●NSns2nsw.name.com2017-07-07 → 2026-08-17 · 3 obs
● 2017-07-07 09:41:42
● 2026-08-17 08:40:08
○NSns3.a2hosting.com2015-07-21 → 2015-07-21 · 4 obs
● 2015-07-21 19:02:06
○ 2015-11-25 00:11:24
○ 2026-08-17 08:40:08
○NSns3.dataplugs.com2015-11-25 → 2016-07-19 · 5 obs
● 2015-11-25 00:11:24
● 2016-07-19 16:47:56
○ 2017-07-07 09:41:42
○ 2026-08-17 08:40:08
●NSns3jkl.name.com2017-07-07 → 2026-08-17 · 3 obs
● 2017-07-07 09:41:42
● 2026-08-17 08:40:08
○NSns4.a2hosting.com2015-07-21 → 2015-07-21 · 4 obs
● 2015-07-21 19:02:06
○ 2015-11-25 00:11:24
○ 2026-08-17 08:40:08
●NSns4bfy.name.com2017-07-07 → 2026-08-17 · 3 obs
● 2017-07-07 09:41:42
● 2026-08-17 08:40:08
●MXalt1.aspmx.l.google.com2015-07-21 → 2026-08-17 · 3 obs
● 2015-07-21 19:02:06
● 2026-08-17 08:40:08
●MXalt2.aspmx.l.google.com2015-07-21 → 2026-08-17 · 3 obs
● 2015-07-21 19:02:06
● 2026-08-17 08:40:08
●MXalt3.aspmx.l.google.com2015-11-25 → 2026-08-17 · 3 obs
● 2015-11-25 00:11:24
● 2026-08-17 08:40:08
●MXalt4.aspmx.l.google.com2015-11-25 → 2026-08-17 · 3 obs
● 2015-11-25 00:11:24
● 2026-08-17 08:40:08
●MXaspmx.l.google.com2015-07-21 → 2026-08-17 · 3 obs
● 2015-07-21 19:02:06
● 2026-08-17 08:40:08
○MXaspmx2.googlemail.com2015-07-21 → 2015-07-21 · 4 obs
● 2015-07-21 19:02:06
○ 2015-11-25 00:11:24
○ 2026-08-17 08:40:08
○MXaspmx3.googlemail.com2015-07-21 → 2015-07-21 · 4 obs
● 2015-07-21 19:02:06
○ 2015-11-25 00:11:24
○ 2026-08-17 08:40:08
○MXbmfc.com2015-07-21 → 2015-11-25 · 5 obs
● 2015-07-21 19:02:06
● 2015-11-25 00:11:24
○ 2016-03-05 00:08:56
○ 2026-08-17 08:40:08
○MXmail.bmfc.com2007-10-27 → 2007-10-27 · 3 obs
○ 2015-07-21 19:02:06
○ 2026-08-17 08:40:08
○A103.44.161.182015-11-25 → 2017-07-07 · 5 obs
● 2015-11-25 00:11:24
● 2017-07-07 09:41:42
○ 2026-03-27 05:50:22
○ 2026-08-17 08:40:08
●A148.66.54.792026-03-27 → 2026-08-17 · 3 obs
● 2026-03-27 05:50:22
● 2026-08-17 08:40:08
○A66.98.154.512007-10-27 → 2007-10-27 · 3 obs
○ 2015-07-21 19:02:06
○ 2026-08-17 08:40:08
○A75.98.175.882015-07-21 → 2015-07-21 · 4 obs
● 2015-07-21 19:02:06
○ 2015-11-25 00:11:24
○ 2026-08-17 08:40:08
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| bmfc.com | ns1fkl.name.com, ns2nsw.name.com, ns3jkl.name.com, ns4bfy.name.com | 8 records |
✅ Authoritative Response
Server:163.114.217.17
NS records: ns1fkl.name.com, ns2nsw.name.com, ns3jkl.name.com, ns4bfy.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for bmfc.com (unsigned zone)
⏱️ Timing
Total: 634ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 148.66.54.79 |
| NS | 4 | ns1fkl.name.com, ns2nsw.name.com... |
| MX | 5 | alt1.aspmx.l.google.com (pri: 5), alt2.aspmx.l.google.com (pri: 5)... |
| TXT | 1 | google-site-verification=gvCaCJRIQSFDhTg |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns1fkl.name.com, ns1fkl.name.com, ns2nsw.name.com...)
Analysis
IP Addresses
bmfc.com resolves to just one IP address, 148.66.54.79.
mail.protege-inc.com, for instance, is one of the other host names sharing IP numbers with bmfc.com.
Name Servers
bmfc.com delegates to five name servers: ns1.name.com, ns1fkl.name.com, ns2nsw.name.com and two others.
There is at least partial name server overlap between bmfc.com and other domains — (0x736578)test.dev, enkisistem.com, time4.news and two more among them.
These name servers regularly appear alongside ns3jkl.name.com, ns4bfy.name.com, ns1cny.name.com and 7 other name servers in NS record sets.
Host names that have two IP addresses:
ns1.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns1fkl.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns2nsw.name.com directs traffic to 163.114.216.49 and 2402:cf80:107::1.
ns3jkl.name.com directs traffic to 163.114.217.17 and 2a00:edc0:107::49.
ns4bfy.name.com directs traffic to 163.114.217.49 and 2402:cf80:107::49.
Both ns1.name.com and ns1fkl.name.com resolve to 2a00:edc0:107::1 IP addresses each.
Both ns1.name.com and ns1fkl.name.com resolve to 163.114.216.17 IP addresses each.
Mail Servers
Five mail servers handle bmfc.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
There is at least a partial MX overlap between bmfc.com and other domains, including ibsanj.org, ns500671.ns500754.ns500754.ns500704.ns500731.ns500704.ns500688.ns500671.ns500666.ns500142.lusty(0x736c7574)z.com, ns500731.ns500671.ns500731.ns500731.ns500742.ns500688.ns500688.ns500671.ns500291.ns500131.lustychickser.com and two others.
These mail servers tend to appear in combination with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.
Host names that have two IP addresses:
aspmx.l.google.com directs traffic to 142.251.163.27 and 2607:f8b0:4004:c08::1a.
alt1.aspmx.l.google.com directs traffic to 192.178.234.26 and 2800:3f0:4003:c14::1b.
alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com directs traffic to 192.178.223.27 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com directs traffic to 172.253.157.27 and 2a00:1450:400c:c23::1a.