device.consulting - dns.ninja

device.consulting

DNSSEC⚠️ Not signed
A95.214.62.254🇷🇺 BEGET-AS95.214.62.0/24 BEGET.RU
NSns1.beget.com
A93.92.81.0
NSns1.beget.pro ⚠️ Not in parent delegation
A93.92.81.0
NSns2.beget.com
A185.50.27.12🇷🇺 BEGET-AS185.50.27.0/24 BEGET.RU
PTRns2.beget.com
NSns2.beget.pro ⚠️ Not in parent delegation
A185.50.27.12🇷🇺 BEGET-AS185.50.27.0/24 BEGET.RU
PTRns2.beget.com
MXmx.yandex.net
A2a02:6b8::311🇷🇺 TELETECH2a02:6b8::/32 Yandex network
PTRmxfront.stable.qloud-b.yandex.net
A77.88.21.249🇷🇺 TELETECH77.88.0.0/18 Yandex enterprise network
TXTv=spf1 include:_spf.yandex.net include:spf.beget.com ~all
SOAns1.beget.comhostmaster@beget.com serial=1768832448

consulting

DNSSEC🔒 Signed (DS record present)
NSv0n0.nic.consulting
NSv0n1.nic.consulting
NSv0n2.nic.consulting
NSv0n3.nic.consulting
NSv2n0.nic.consulting
NSv2n1.nic.consulting
SOAv0n0.nic.consultinghostmaster@donuts.email serial=1784677555

Subdomains

Same first word

Similar names

DNS History

18 records (6 active, 12 former)

20192020202120222023202420252026NSns1.beget.comns1.beget.prons2.beget.comns2.beget.prodnsproxy1.fm.nic.rudnsproxy2.fm.nic.runs1.linode.comns2.linode.comns3.linode.comns4.linode.comns5.linode.comMXmx.yandex.netnomail.nic.ruA95.214.62.254176.58.114.942a01:7e00::f03c:91ff:fe56:f7ef31.177.76.3231.177.80.32
NSdnsproxy1.fm.nic.ru2026-06-16 → 2026-06-17 · 5 obs
○ 2026-06-07 15:25:12
● 2026-06-16 12:31:12
● 2026-06-17 12:40:14
○ 2026-06-17 19:05:18
○ 2026-07-22 00:13:56
NSdnsproxy2.fm.nic.ru2026-06-16 → 2026-06-17 · 5 obs
○ 2026-06-07 15:25:12
● 2026-06-16 12:31:12
● 2026-06-17 12:40:14
○ 2026-06-17 19:05:18
○ 2026-07-22 00:13:56
NSns1.beget.com2026-02-15 → 2026-07-22 · 7 obs
○ 2018-10-27 02:00:16
● 2026-02-15 15:38:20
● 2026-06-07 15:25:12
○ 2026-06-16 12:31:12
○ 2026-06-17 12:40:14
● 2026-06-17 19:05:18
● 2026-07-22 00:13:56
NSns1.beget.pro2026-02-15 → 2026-07-22 · 7 obs
○ 2018-10-27 02:00:16
● 2026-02-15 15:38:20
● 2026-06-07 15:25:12
○ 2026-06-16 12:31:12
○ 2026-06-17 12:40:14
● 2026-06-17 19:05:18
● 2026-07-22 00:13:56
NSns1.linode.com2018-10-27 → 2018-10-27 · 3 obs
● 2018-10-27 02:00:16
○ 2026-02-15 15:38:20
○ 2026-07-22 00:13:56
NSns2.beget.com2026-02-15 → 2026-07-22 · 7 obs
○ 2018-10-27 02:00:16
● 2026-02-15 15:38:20
● 2026-06-07 15:25:12
○ 2026-06-16 12:31:12
○ 2026-06-17 12:40:14
● 2026-06-17 19:05:18
● 2026-07-22 00:13:56
NSns2.beget.pro2026-02-15 → 2026-07-22 · 7 obs
○ 2018-10-27 02:00:16
● 2026-02-15 15:38:20
● 2026-06-07 15:25:12
○ 2026-06-16 12:31:12
○ 2026-06-17 12:40:14
● 2026-06-17 19:05:18
● 2026-07-22 00:13:56
NSns2.linode.com2018-10-27 → 2018-10-27 · 3 obs
● 2018-10-27 02:00:16
○ 2026-02-15 15:38:20
○ 2026-07-22 00:13:56
NSns3.linode.com2018-10-27 → 2018-10-27 · 3 obs
● 2018-10-27 02:00:16
○ 2026-02-15 15:38:20
○ 2026-07-22 00:13:56
NSns4.linode.com2018-10-27 → 2018-10-27 · 3 obs
● 2018-10-27 02:00:16
○ 2026-02-15 15:38:20
○ 2026-07-22 00:13:56
NSns5.linode.com2018-10-27 → 2018-10-27 · 3 obs
● 2018-10-27 02:00:16
○ 2026-02-15 15:38:20
○ 2026-07-22 00:13:56
MXmx.yandex.net2018-10-27 → 2026-07-22 · 6 obs
● 2018-10-27 02:00:16
● 2026-06-07 15:25:12
○ 2026-06-16 12:31:12
○ 2026-06-17 12:40:14
● 2026-06-17 19:05:18
● 2026-07-22 00:13:56
MXnomail.nic.ru2026-06-16 → 2026-06-17 · 5 obs
○ 2026-06-07 15:25:12
● 2026-06-16 12:31:12
● 2026-06-17 12:40:14
○ 2026-06-17 19:05:18
○ 2026-07-22 00:13:56
A176.58.114.942018-10-27 → 2018-10-27 · 3 obs
● 2018-10-27 02:00:16
○ 2026-02-15 15:38:20
○ 2026-07-22 00:13:56
A2a01:7e00::f03c:91ff:fe56:f7ef2018-10-27 → 2018-10-27 · 3 obs
● 2018-10-27 02:00:16
○ 2026-02-15 15:38:20
○ 2026-07-22 00:13:56
A31.177.76.322026-06-16 → 2026-06-17 · 5 obs
○ 2026-06-07 15:25:12
● 2026-06-16 12:31:12
● 2026-06-17 12:40:14
○ 2026-06-17 19:05:18
○ 2026-07-22 00:13:56
A31.177.80.322026-06-16 → 2026-06-17 · 5 obs
○ 2026-06-07 15:25:12
● 2026-06-16 12:31:12
● 2026-06-17 12:40:14
○ 2026-06-17 19:05:18
○ 2026-07-22 00:13:56
A95.214.62.2542026-02-15 → 2026-07-22 · 7 obs
○ 2018-10-27 02:00:16
● 2026-02-15 15:38:20
● 2026-06-07 15:25:12
○ 2026-06-16 12:31:12
○ 2026-06-17 12:40:14
● 2026-06-17 19:05:18
● 2026-07-22 00:13:56

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
consultingv0n0.nic.consulting, v0n1.nic.consulting, v0n2.nic.consulting, v0n3.nic.consulting...12 records
device.consultingns1.beget.com, ns2.beget.com-

✅ Authoritative Response

Server:185.50.27.12

NS records: ns1.beget.com, ns2.beget.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for device.consulting (unsigned zone)

⏱️ Timing

Total: 1191ms | Queries: -

📄 Records

TypeCountSample Data
A195.214.62.254
NS4ns2.beget.pro, ns1.beget.pro...
MX1mx.yandex.net (pri: 10)
TXT1v=spf1 include:_spf.yandex.net include:s
SOA1ns1.beget.com hostmaster.beget.com

📌 Glue Records Collected

Total: 12

In-bailiwick: 12 (v2n1.nic.consulting, v2n0.nic.consulting, v0n3.nic.consulting...)

Analysis

Hierarchy

www.device.consulting is a subdomain of device.consulting.

IP Addresses

device.consulting has exactly one IP address — 95.214.62.254.

www.device.consulting, for instance, is one of the other host names sharing IP numbers with device.consulting.

Name Servers

Four name servers handle the delegation for device.consulting: ns1.beget.com, ns2.beget.com, ns1.beget.pro and ns2.beget.pro.

The name servers of device.consulting overlap at least partially with those of other domains — among them itfoto.ru, dsog.ru, docforyou.ru and two more.

These name servers commonly appear alongside the name servers ns1.beget.ru and ns2.beget.ru.

Each of the host names ns1.beget.com, ns2.beget.com, ns1.beget.pro and ns2.beget.pro has one IP address: ns1.beget.com resolves to 93.92.81.0, ns2.beget.com resolves to 185.50.27.12, ns1.beget.pro resolves to 93.92.81.0 and ns2.beget.pro resolves to 185.50.27.12.

Both ns1.beget.com and ns1.beget.pro resolve to 93.92.81.0 IP addresses each.

Both ns2.beget.com and ns2.beget.pro resolve to 185.50.27.12 IP addresses each.

Mail Servers

device.consulting uses one mail server — mx.yandex.net.

The mail server setup of device.consulting matches that of other domains such as krasnostop.ru, akademservis.com, 1bpk.ru and two others.

device.consulting has mail servers in common with other domains — fitnessfreedom.ru being one example.

mx.yandex.net resolves to two IP numbers — 77.88.21.249 and 2a02:6b8::311.