ryefield.com - dns.ninja
ryefield.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=1785045777 | ||||||
Subdomains
www.ryefield.com |
Same first word
Similar names
DNS History
13 records (8 active, 5 former)
○NSns1.afternic.com2015-08-13 → 2017-04-01 · 4 obs
● 2017-04-01 06:05:42
○ 2020-04-12 13:47:30
○ 2026-07-26 06:14:38
●NSns1.beget.com2026-04-03 → 2026-07-26 · 3 obs
● 2026-04-03 09:38:48
● 2026-07-26 06:14:38
●NSns1.beget.pro2026-04-03 → 2026-07-26 · 3 obs
● 2026-04-03 09:38:48
● 2026-07-26 06:14:38
○NSns1.namefind.com2020-04-12 → 2020-04-12 · 4 obs
● 2020-04-12 13:47:30
○ 2026-04-03 09:38:48
○ 2026-07-26 06:14:38
●NSns2.beget.com2026-04-03 → 2026-07-26 · 3 obs
● 2026-04-03 09:38:48
● 2026-07-26 06:14:38
●NSns2.beget.pro2026-04-03 → 2026-07-26 · 3 obs
● 2026-04-03 09:38:48
● 2026-07-26 06:14:38
○NSns2.namefind.com2020-04-12 → 2020-04-12 · 4 obs
● 2020-04-12 13:47:30
○ 2026-04-03 09:38:48
○ 2026-07-26 06:14:38
●A116.203.41.2102026-04-03 → 2026-07-26 · 3 obs
● 2026-04-03 09:38:48
● 2026-07-26 06:14:38
●A168.119.123.1312026-04-03 → 2026-07-26 · 3 obs
● 2026-04-03 09:38:48
● 2026-07-26 06:14:38
○A184.168.221.1042015-08-13 → 2017-04-01 · 4 obs
● 2017-04-01 06:05:42
○ 2020-04-12 13:47:30
○ 2026-07-26 06:14:38
○A35.186.238.1012020-04-12 → 2020-04-12 · 4 obs
● 2020-04-12 13:47:30
○ 2026-04-03 09:38:48
○ 2026-07-26 06:14:38
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | k.gtld-servers.net, f.gtld-servers.net, d.gtld-servers.net, b.gtld-servers.net... | - |
| ryefield.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 ryefield.com (unsigned zone)
⏱️ Timing
Total: 908ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 116.203.41.210, 168.119.123.131 |
| NS | 4 | ns2.beget.pro, ns1.beget.pro... |
| 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 |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.beget.com, ns2.beget.com)
Analysis
Hierarchy
www.ryefield.com is a subdomain of ryefield.com.
IP Addresses
ryefield.com points to the IP addresses 116.203.41.210 and 168.119.123.131
Among the host names that share IP numbers with ryefield.com is www.ryefield.com, as one example.
Name Servers
The NS records for ryefield.com point to four name servers: ns1.beget.com, ns2.beget.com, ns1.beget.pro and ns2.beget.pro.
The name servers of ryefield.com overlap at least partially with those of other domains — among them paustovskiy-lit.ru, sbornikprog.ru, npft.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.
ns1.beget.com and ns1.beget.pro each have 93.92.81.0 IP addresses.
ns2.beget.com and ns2.beget.pro each have 185.50.27.12 IP addresses.
Mail Servers
ryefield.com is served by two mail servers, mx1.beget.com and mx2.beget.com.
Among the domains sharing a mail server setup with ryefield.com are deliverify-work.ru, xn--80afdc0adyaikz4j.xn--p1ai, energosnab-spb.ru and two others.
ryefield.com has mail servers in common with other domains — fishout.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.
mx1.beget.com and mx2.beget.com each have 185.78.30.95 IP addresses.
mx1.beget.com and mx2.beget.com each have 185.78.30.126 IP addresses.