devdata.org - dns.ninja
devdata.org
org
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a0.org.afilias-nst.info ⭐ ⚠️ Not in parent delegation | ||||||
| NS | a2.org.afilias-nst.info ⚠️ Not in parent delegation | ||||||
| NS | b0.org.afilias-nst.org | ||||||
| NS | b2.org.afilias-nst.org | ||||||
| NS | c0.org.afilias-nst.info ⚠️ Not in parent delegation | ||||||
| NS | d0.org.afilias-nst.org | ||||||
| SOA | a0.org.afilias-nst.infohostmaster@donuts.email serial=1782800833 | ||||||
Same first word
devdata.co |
devdata.de |
devdata.com.br |
devdata.fr |
devdata.info |
devdata.org |
devdata.it |
devdata.nl |
devdata.eu |
devdata.net |
devdata.com |
Similar names
DNS History
12 records (7 active, 5 former)
●NSns1.beget.com2026-02-18 → 2026-06-30 · 3 obs
● 2026-02-18 04:26:12
● 2026-06-30 07:07:16
●NSns1.beget.pro2026-02-18 → 2026-06-30 · 3 obs
● 2026-02-18 04:26:12
● 2026-06-30 07:07:16
●NSns2.beget.com2026-02-18 → 2026-06-30 · 3 obs
● 2026-02-18 04:26:12
● 2026-06-30 07:07:16
●NSns2.beget.pro2026-02-18 → 2026-06-30 · 3 obs
● 2026-02-18 04:26:12
● 2026-06-30 07:07:16
○NSns23.domaincontrol.com2015-07-15 → 2017-04-03 · 4 obs
● 2017-04-03 15:08:28
○ 2026-02-18 04:26:12
○ 2026-06-30 07:07:16
○NSns24.domaincontrol.com2015-07-15 → 2017-04-03 · 4 obs
● 2017-04-03 15:08:28
○ 2026-02-18 04:26:12
○ 2026-06-30 07:07:16
○MXmailstore1.secureserver.net2015-07-15 → 2017-04-03 · 4 obs
● 2017-04-03 15:08:28
○ 2026-02-18 04:26:12
○ 2026-06-30 07:07:16
●MXmx1.beget.com2026-02-18 → 2026-06-30 · 3 obs
● 2026-02-18 04:26:12
● 2026-06-30 07:07:16
●MXmx2.beget.com2026-02-18 → 2026-06-30 · 3 obs
● 2026-02-18 04:26:12
● 2026-06-30 07:07:16
○MXsmtp.secureserver.net2015-07-15 → 2017-04-03 · 4 obs
● 2017-04-03 15:08:28
○ 2026-02-18 04:26:12
○ 2026-06-30 07:07:16
●A45.130.41.812026-02-18 → 2026-06-30 · 3 obs
● 2026-02-18 04:26:12
● 2026-06-30 07:07:16
○A50.63.202.612015-07-15 → 2017-04-03 · 4 obs
● 2017-04-03 15:08:28
○ 2026-02-18 04:26:12
○ 2026-06-30 07:07:16
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| org | b0.org.afilias-nst.org, b2.org.afilias-nst.org, d0.org.afilias-nst.org | - |
| devdata.org | ns2.beget.pro, ns1.beget.com, ns1.beget.pro, ns2.beget.com | - |
✅ Authoritative Response
Server:185.50.27.12
NS records: ns2.beget.pro, ns1.beget.com, ns1.beget.pro, ns2.beget.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for devdata.org (unsigned zone)
⏱️ Timing
Total: 896ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 45.130.41.81 |
| NS | 4 | ns1.beget.com, ns2.beget.com... |
| MX | 2 | mx1.beget.com (pri: 10), mx2.beget.com (pri: 20) |
| TXT | 1 | v=spf1 redirect=beget.com |
| SOA | 1 | ns1.beget.com hostmaster.beget.com |
Analysis
IP Addresses
devdata.org directs to one IP number, which is 45.130.41.81.
Among the host names that share IP numbers with devdata.org are blogbaster.org, shini.ru, dush-kz.ru and two others.
Name Servers
The domain devdata.org is delegated to these four name servers: ns1.beget.com, ns2.beget.com, ns1.beget.pro and ns2.beget.pro.
The name servers of devdata.org overlap at least partially with those of other domains — among them grebenukm-anomaliya.store, npf-paker.com, xn----7sbbb1an9cmf8j.xn--p1ai 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
The MX records for devdata.org point to two mail servers: mx1.beget.com and mx2.beget.com.
devdata.org has the same mail server arrangement as a number of other domains, for example www.demosistema.ru, doma-darom.ru, promoug.ru and two more.
devdata.org has mail servers in common with other domains — dveriprofy.ru being one example.
Each of the hosts mx1.beget.com and mx2.beget.com points to four IP numbers: mx1.beget.com directs to 5.101.158.67, 5.101.158.68, 185.78.30.95 and 185.78.30.126, and mx2.beget.com directs to 185.78.30.48, 185.78.30.71, 185.78.30.95 and 185.78.30.126.
Both mx1.beget.com and mx2.beget.com resolve to 185.78.30.95 IP addresses each.
Both mx1.beget.com and mx2.beget.com resolve to 185.78.30.126 IP addresses each.