mfctrade.com - robtex.com
mfctrade.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 178.210.162.88🇹🇷 gibirnet-tr178.210.162.0/24 GIBIRNET | ||||||
| NS | dns1.markum.net ⭐ | ||||||
| A | 178.210.170.4🇹🇷 NETFACTOR-ASN178.210.170.0/24 | ||||||
| NS | dns2.markum.net | ||||||
| A | 178.210.178.4🇹🇷 NETFACTOR-ASN178.210.178.0/24 | ||||||
| MX | mx.yandex.net ⭐ | ||||||
| A | 2a02:6b8::311🇷🇺 TELETECH2a02:6b8::/32 Yandex network | ||||||
| PTR | mxfront.stable.qloud-b.yandex.net | ||||||
| A | 77.88.21.249🇷🇺 TELETECH77.88.0.0/18 Yandex enterprise network | ||||||
| PTR | mxfront.stable.qloud-b.yandex.net | ||||||
| TXT | yandex-verification: b10697ee4fb1b26a | ||||||
| TXT | v=spf1 redirect=_spf.yandex.net | ||||||
| TXT | b10697ee4fb1b26a | ||||||
| SOA | dns1.markum.netdestek@markum.net 2017-07-27 #10 | ||||||
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=1774369342 | ||||||
Same first word
mfctrade.com |
Similar names
DNS History
7 records (4 active, 3 former)
●NSdns1.markum.net2015-07-01 → 2026-03-24 · 2 obs
● 2026-03-24 16:49:50
●NSdns2.markum.net2015-07-01 → 2026-03-24 · 2 obs
● 2026-03-24 16:49:50
○MXmail.mfctrade.com2015-07-01 → 2016-01-26 · 4 obs
● 2016-01-26 05:12:22
○ 2016-04-16 19:50:06
○ 2026-03-24 16:49:50
●MXmx.yandex.net2026-03-22 → 2026-03-24 · 3 obs
● 2026-03-22 17:53:28
● 2026-03-24 16:49:50
○MXmx1.mfctrade.com2016-04-16 → 2017-05-16 · 5 obs
● 2016-04-16 19:50:06
● 2017-05-16 05:07:40
○ 2026-03-22 17:53:28
○ 2026-03-24 16:49:50
○MXmx2.mfctrade.com2016-04-16 → 2017-05-16 · 5 obs
● 2016-04-16 19:50:06
● 2017-05-16 05:07:40
○ 2026-03-22 17:53:28
○ 2026-03-24 16:49:50
●A178.210.162.882015-07-01 → 2026-03-24 · 2 obs
● 2026-03-24 16:49:50
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | e.gtld-servers.net, b.gtld-servers.net, k.gtld-servers.net, j.gtld-servers.net... | - |
| mfctrade.com | dns1.markum.net, dns2.markum.net | - |
✅ Authoritative Response
Server:178.210.178.4
NS records: dns1.markum.net, dns2.markum.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for mfctrade.com (unsigned zone)
⏱️ Timing
Total: 753ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 178.210.162.88 |
| NS | 2 | dns2.markum.net, dns1.markum.net |
| MX | 1 | mx.yandex.net (pri: 10) |
| TXT | 3 | v=spf1 redirect=_spf.yandex.net, yandex-verification: b10697ee4fb1b26a... |
| SOA | 1 | dns1.markum.net destek.markum.net |
Analysis
IP Addresses
mfctrade.com points to IP number 178.210.162.88.
Name Servers
mfctrade.com is delegated to two name servers: dns1.markum.net and dns2.markum.net.
mfctrade.com uses the same name server setup as other domains such as admma.org, inotrim.com.tr, kocogullaripalet.com, akkalip.com and kerimoglulastik.com.
mfctrade.com shares name servers with other domains at least partially, for example ariser.com.tr, gentra.com.tr, destanreklam.com.tr, hiziroto.com.tr and abmgrinding.com.
These name servers are commonly used with the name servers ns1.markum.net and ns2.markum.net.
Host names with one IP number:
dns1.markum.net points to: 178.210.170.4.
dns2.markum.net points to: 178.210.178.4.
Mail Servers
mfctrade.com is handled by a single mail server, mx.yandex.net.
mfctrade.com shares the same mail server setup as other domains, for instance exws.ru, antgroupp.ru, 1-yar.ru, bakshutova.ru and firsov.id.lv.
mfctrade.com shares mail servers with other domains at least partially; for instance xn--80aheadlg5acc8a5e9b.xn--p1ai, torkretstroi.ru, www.rukodelie.ru, xn----ctbffqewfjsg.xn--p1ai and xn----7sbabaisvvdl4aebu3b5gxc.xn--p1ai.
mx.yandex.net resolves to two IPs: 2a02:6b8::311 and 77.88.21.249.