fire-blaze.com - robtex.com
fire-blaze.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=1784396382 | ||||||
Same first word
fire-blaze.com |
Similar names
DNS History
19 records (7 active, 12 former)
○NSns.masterhost.ru2016-04-22 → 2017-04-20 · 4 obs
● 2017-04-20 15:19:28
○ 2026-06-19 11:10:18
○ 2026-07-18 17:51:08
●NSns1.beget.com2026-06-19 → 2026-07-18 · 3 obs
● 2026-06-19 11:10:18
● 2026-07-18 17:51:08
●NSns1.beget.pro2026-06-19 → 2026-07-18 · 3 obs
● 2026-06-19 11:10:18
● 2026-07-18 17:51:08
○NSns1.masterhost.ru2016-04-22 → 2017-04-20 · 4 obs
● 2017-04-20 15:19:28
○ 2026-06-19 11:10:18
○ 2026-07-18 17:51:08
●NSns2.beget.com2026-06-19 → 2026-07-18 · 3 obs
● 2026-06-19 11:10:18
● 2026-07-18 17:51:08
●NSns2.beget.pro2026-06-19 → 2026-07-18 · 3 obs
● 2026-06-19 11:10:18
● 2026-07-18 17:51:08
○NSns2.masterhost.ru2016-04-22 → 2017-04-20 · 4 obs
● 2017-04-20 15:19:28
○ 2026-06-19 11:10:18
○ 2026-07-18 17:51:08
●MXmx.yandex.net2016-04-22 → 2026-07-18 · 2 obs
● 2026-07-18 17:51:08
●MXmx2.beget.com2026-06-19 → 2026-07-18 · 3 obs
● 2026-06-19 11:10:18
● 2026-07-18 17:51:08
○A2a00:15f8:a000:5:1:11:6:7c0c2016-04-22 → 2017-04-20 · 4 obs
● 2017-04-20 15:19:28
○ 2026-06-19 11:10:18
○ 2026-07-18 17:51:08
○A2a00:15f8:a000:5:1:12:6:7c0c2016-04-22 → 2017-04-20 · 4 obs
● 2017-04-20 15:19:28
○ 2026-06-19 11:10:18
○ 2026-07-18 17:51:08
○A2a00:15f8:a000:5:1:13:6:7c0c2016-04-22 → 2017-04-20 · 4 obs
● 2017-04-20 15:19:28
○ 2026-06-19 11:10:18
○ 2026-07-18 17:51:08
○A2a00:15f8:a000:5:1:14:6:7c0c2016-04-22 → 2017-04-20 · 4 obs
● 2017-04-20 15:19:28
○ 2026-06-19 11:10:18
○ 2026-07-18 17:51:08
●A45.130.41.1572026-06-19 → 2026-07-18 · 3 obs
● 2026-06-19 11:10:18
● 2026-07-18 17:51:08
○A90.156.201.1112017-04-20 → 2017-04-20 · 4 obs
● 2017-04-20 15:19:28
○ 2026-06-19 11:10:18
○ 2026-07-18 17:51:08
○A90.156.201.162016-04-22 → 2017-04-20 · 4 obs
● 2017-04-20 15:19:28
○ 2026-06-19 11:10:18
○ 2026-07-18 17:51:08
○A90.156.201.282016-04-22 → 2016-04-22 · 3 obs
○ 2017-04-20 15:19:28
○ 2026-07-18 17:51:08
○A90.156.201.552016-04-22 → 2017-04-20 · 4 obs
● 2017-04-20 15:19:28
○ 2026-06-19 11:10:18
○ 2026-07-18 17:51:08
○A90.156.201.972016-04-22 → 2017-04-20 · 4 obs
● 2017-04-20 15:19:28
○ 2026-06-19 11:10:18
○ 2026-07-18 17:51: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... | - |
| fire-blaze.com | ns1.beget.pro, ns2.beget.pro, ns1.beget.com, ns2.beget.com | 2 records |
✅ Authoritative Response
Server:93.92.81.0
NS records: ns1.beget.pro, ns2.beget.pro, ns1.beget.com, ns2.beget.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for fire-blaze.com (unsigned zone)
⏱️ Timing
Total: 2778ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 45.130.41.157 |
| NS | 4 | ns2.beget.pro, ns1.beget.pro... |
| MX | 2 | mx.yandex.net (pri: 10), mx2.beget.com (pri: 20) |
| TXT | 1 | v=spf1 redirect=_spf.yandex.net |
| SOA | 1 | ns1.beget.com hostmaster.beget.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.beget.com, ns2.beget.com)
Analysis
IP Addresses
fire-blaze.com resolves to one IP address: 45.130.41.157.
axioma.co, nizhny-novgorod.tutmnogo.com, promresurss.ru and two other host names share IP numbers with fire-blaze.com.
Name Servers
The authoritative name servers for fire-blaze.com are ns1.beget.com, ns2.beget.com, ns1.beget.pro and ns2.beget.pro.
At least some of fire-blaze.com's name servers are shared with other domains, for example logopedshop.ru, ledebut.ru, shtabeler.ru and two more.
These name servers tend to be deployed in combination with the name servers ns1.beget.ru and ns2.beget.ru.
ns1.beget.com, ns2.beget.com, ns1.beget.pro and ns2.beget.pro each point to exactly one IP address. ns1.beget.com directs to 93.92.81.0, ns2.beget.com directs to 185.50.27.12, ns1.beget.pro directs to 93.92.81.0 and ns2.beget.pro directs to 185.50.27.12. Two pairs share an IP: ns1.beget.com and ns1.beget.pro share 93.92.81.0, and ns2.beget.com and ns2.beget.pro share 185.50.27.12.
Host names pointing to 93.92.81.0 IP addresses: ns1.beget.com and ns1.beget.pro.
Host names pointing to 185.50.27.12 IP addresses: ns2.beget.com and ns2.beget.pro.
Mail Servers
Mail for fire-blaze.com is handled by two mail servers — mx2.beget.com and mx.yandex.net.
fire-blaze.com uses an identical mail server configuration to several other domains — among them lspu-online.ru, www.red-g.ru, multstory.com and two more.
fire-blaze.com has at least partial mail server overlap with other domains such as germetaks.ru, fpc24.ru, npoarsenal.ru and two more.
This set of mail servers commonly appears together with the mail servers mx1.beget.com.
Hosts that point to four IP numbers:
mx2.beget.com directs to 185.78.30.48, 185.78.30.71, 185.78.30.95 and 185.78.30.126.
Hostnames that resolve to two IP addresses:
mx.yandex.net has two IP addresses: 77.88.21.249 and 2a02:6b8::311.