fserver.ru - dns.ninja
fserver.ru
| DNSSEC | ⚠️ Not signed | ||||||
| A | 193.38.55.27🇳🇱 THE193.38.55.0/24 | ||||||
| NS | dns1.yandex.net ⭐ ⚠️ Not in zone NS records | ||||||
| A | 2a02:6b8::213🇷🇺 TELETECH2a02:6b8::/32 Yandex network | ||||||
| PTR | dns1.yandex.net | ||||||
| A | 213.180.204.213🇷🇺 TELETECH213.180.192.0/19 Yandex network | ||||||
| PTR | dns1.yandex.net | ||||||
| NS | dns2.yandex.net ⚠️ Not in zone NS records | ||||||
| A | 2a02:6b8:0:1::213🇷🇺 TELETECH2a02:6b8::/32 Yandex network | ||||||
| PTR | dns2.yandex.net | ||||||
| A | 93.158.134.213🇷🇺 TELETECH93.158.128.0/18 Yandex enterprise network | ||||||
| PTR | dns2.yandex.net | ||||||
| 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 | v=spf1 redirect=_spf.yandex.net | ||||||
| TXT | yandex-verification: 47e59268f9c34be0 | ||||||
| SOA | dns1.yandex.netdns-hosting@yandex.ru serial=31 | ||||||
ru
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.dns.ripn.net ⭐ | ||||||
| NS | b.dns.ripn.net | ||||||
| NS | c.tld-servers.ru | ||||||
| NS | d.dns.ripn.net | ||||||
| NS | e.dns.ripn.net | ||||||
| NS | f.dns.ripn.net | ||||||
| SOA | a.dns.ripn.nethostmaster@ripn.net serial=4069851 | ||||||
Previously NS for
Subdomains
mail.fserver.ru |
Same first word
fserver.cn |
fserver.sakura.ne.jp |
fserver.ir |
fserver.eu |
fserver.org |
fserver.ru |
fserver.us |
fserver.net |
fserver.de |
fserver.com |
fserver.co.uk |
Similar names
freevrs.com |
fervers.net |
serverf.net |
freevrs.org |
fervers.com |
rsvfree.com |
revesfr.org |
verfers.de |
srvfree.fr |
servref.com |
fresver.com.sg |
freesrv.org |
freesrv.de |
freevrs.net |
freevrs.co.uk |
DNS History
17 records (4 active, 13 former)
○NS82.199.120.1732015-05-22 → 2015-05-22 · 3 obs
○ 2015-09-06 02:09:26
○ 2026-08-03 10:36:56
○NS83.229.149.1492015-05-22 → 2015-05-22 · 3 obs
○ 2015-09-06 02:09:26
○ 2026-08-03 10:36:56
○NSdana.ns.cloudflare.com2016-04-16 → 2017-01-25 · 5 obs
● 2016-04-16 07:05:32
● 2017-01-25 07:40:38
○ 2026-02-17 01:03:02
○ 2026-08-03 10:36:56
●NSdns1.yandex.net2026-02-17 → 2026-08-03 · 3 obs
● 2026-02-17 01:03:02
● 2026-08-03 10:36:56
●NSdns2.yandex.net2026-02-17 → 2026-08-03 · 3 obs
● 2026-02-17 01:03:02
● 2026-08-03 10:36:56
○NSgeorge.ns.cloudflare.com2016-04-16 → 2017-01-25 · 5 obs
● 2016-04-16 07:05:32
● 2017-01-25 07:40:38
○ 2026-02-17 01:03:02
○ 2026-08-03 10:36:56
○NSns1.fserver.ru2015-05-22 → 2016-01-16 · 4 obs
● 2016-01-16 20:22:50
○ 2016-04-16 07:05:32
○ 2026-08-03 10:36:56
○NSns2.fserver.ru2015-09-06 → 2016-01-16 · 5 obs
● 2015-09-06 02:09:26
● 2016-01-16 20:22:50
○ 2016-04-16 07:05:32
○ 2026-08-03 10:36:56
○MXmail.fserver.ru2015-05-22 → 2016-01-16 · 4 obs
● 2016-01-16 20:22:50
○ 2016-04-16 07:05:32
○ 2026-08-03 10:36:56
●MXmx.yandex.net2016-04-16 → 2026-08-03 · 3 obs
● 2016-04-16 07:05:32
● 2026-08-03 10:36:56
○A104.28.20.1232016-04-16 → 2016-12-16 · 5 obs
● 2016-04-16 07:05:32
● 2016-12-16 09:20:56
○ 2017-01-11 13:00:28
○ 2026-08-03 10:36:56
○A104.28.21.1232016-04-16 → 2016-12-16 · 5 obs
● 2016-04-16 07:05:32
● 2016-12-16 09:20:56
○ 2017-01-11 13:00:28
○ 2026-08-03 10:36:56
●A193.38.55.272026-02-17 → 2026-08-03 · 3 obs
● 2026-02-17 01:03:02
● 2026-08-03 10:36:56
○A2400:cb00:2048:1::681c:147b2016-12-16 → 2016-12-16 · 4 obs
● 2016-12-16 09:20:56
○ 2017-01-11 13:00:28
○ 2026-08-03 10:36:56
○A2400:cb00:2048:1::681c:157b2016-12-16 → 2016-12-16 · 4 obs
● 2016-12-16 09:20:56
○ 2017-01-11 13:00:28
○ 2026-08-03 10:36:56
○A82.199.120.1732015-05-22 → 2016-01-16 · 4 obs
● 2016-01-16 20:22:50
○ 2016-04-16 07:05:32
○ 2026-08-03 10:36:56
○A95.165.155.2442017-01-11 → 2017-01-25 · 5 obs
● 2017-01-11 13:00:28
● 2017-01-25 07:40:38
○ 2026-02-17 01:03:02
○ 2026-08-03 10:36:56
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| ru | b.dns.ripn.net, c.tld-servers.ru, d.dns.ripn.net, e.dns.ripn.net... | 12 records |
| fserver.ru | dns1.yandex.net, dns2.yandex.net | - |
✅ Authoritative Response
Server:93.158.134.213
NS records: dns1.yandex.net, dns2.yandex.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for fserver.ru (unsigned zone)
⏱️ Timing
Total: 1942ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | dns2.yandex.net, dns1.yandex.net |
| MX | 1 | mx.yandex.net (pri: 10) |
| SOA | 1 | dns1.yandex.net dns-hosting.yandex.ru |
📌 Glue Records Collected
Total: 12
In-bailiwick: 2 (c.tld-servers.ru, c.tld-servers.ru)
Out-of-bailiwick: 10 (f.dns.ripn.net, e.dns.ripn.net, d.dns.ripn.net...)
Analysis
Hierarchy
mail.fserver.ru is a subdomain of fserver.ru.
IP Addresses
fserver.ru has exactly one IP address — 193.38.55.27.
Name Servers
Two name servers handle the delegation for fserver.ru: dns1.yandex.net and dns2.yandex.net.
The name server configuration of fserver.ru is shared with other domains, for instance signotec.ru, lifestar.ru, loo.by and two others.
The name servers of fserver.ru overlap at least partially with those of other domains — among them crm4you.ru, korb.ru, sauna.ru and two more.
These name servers commonly appear alongside the name servers dns1.yandex.ru and dns2.yandex.ru.
dns1.yandex.net and dns2.yandex.net both carry two IP addresses. The A records for dns1.yandex.net are 213.180.204.213 and 2a02:6b8::213; the A records for dns2.yandex.net are 93.158.134.213 and 2a02:6b8:0:1::213.
Mail Servers
fserver.ru uses one mail server — mx.yandex.net.
The mail server setup of fserver.ru matches that of other domains such as mailinghaus.com, bar-style.ru, tech-construction.ru and two others.
The mail servers for fserver.ru overlap at least partially with those of other domains, including 1nos.ru and cabinet380.ru.
mx.yandex.net resolves to two IP numbers — 77.88.21.249 and 2a02:6b8::311.