fork.su - dns.ninja

fork.su

DNSSEC⚠️ Not signed
A89.104.94.125🇷🇺 AS-REGRU89.104.94.0/24 Reg.Ru
PTR89-104-94-125.cloudvps.regruhosting.ru
NSdns1.yandex.net
A2a02:6b8::213🇷🇺 TELETECH2a02:6b8::/32 Yandex network
PTRdns1.yandex.net
A213.180.204.213🇷🇺 TELETECH213.180.192.0/19 Yandex network
PTRdns1.yandex.net
NSdns2.yandex.net
A2a02:6b8:0:1::213🇷🇺 TELETECH2a02:6b8::/32 Yandex network
PTRdns2.yandex.net
A93.158.134.213🇷🇺 TELETECH93.158.128.0/18
PTRdns2.yandex.net
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
PTRmxfront.stable.qloud-b.yandex.net
TXTv=spf1 ip4:82.146.63.205 include:_spf.yandex.net ~all
SOAdns1.yandex.netdns-hosting@yandex.ru serial=37

su

DNSSEC🔒 Signed (DS record present)
NSa.dns.ripn.net
NSb.dns.ripn.net
NSd.dns.ripn.net
NSe.dns.ripn.net
NSf.dns.ripn.net
SOAa.dns.ripn.nethostmaster@ripn.net serial=650209966

Subdomains

Same first word

Similar names

DNS History

20 records (4 active, 16 former)

20162017201820192020202120222023202420252026NSdns1.yandex.netdns2.yandex.nethostb.hayazg.netns1.hayazg.netns2.hayazg.netns3.hayazg.netns4.hayazg.netMXmx.yandex.netalt1.aspmx.l.google.comalt2.aspmx.l.google.comaspmx.l.google.comaspmx2.googlemail.comaspmx3.googlemail.comaspmx4.googlemail.comaspmx5.googlemail.comA89.104.94.125116.202.249.232144.76.114.2425.9.161.21182.112.189.227
NSdns1.yandex.net2017-07-17 → 2026-07-25 · 3 obs
○ 2016-11-19 11:30:40
● 2017-07-17 19:05:14
● 2026-07-25 16:34:36
NSdns2.yandex.net2017-07-17 → 2026-07-25 · 3 obs
○ 2016-11-19 11:30:40
● 2017-07-17 19:05:14
● 2026-07-25 16:34:36
NShostb.hayazg.net2015-09-01 → 2016-11-19 · 4 obs
● 2015-09-01 13:46:38
● 2016-11-19 11:30:40
○ 2017-07-17 19:05:14
○ 2026-07-25 16:34:36
NSns1.hayazg.net2015-09-01 → 2016-11-19 · 4 obs
● 2015-09-01 13:46:38
● 2016-11-19 11:30:40
○ 2017-07-17 19:05:14
○ 2026-07-25 16:34:36
NSns2.hayazg.net2015-09-01 → 2016-11-19 · 4 obs
● 2015-09-01 13:46:38
● 2016-11-19 11:30:40
○ 2017-07-17 19:05:14
○ 2026-07-25 16:34:36
NSns3.hayazg.net2015-09-01 → 2016-11-19 · 4 obs
● 2015-09-01 13:46:38
● 2016-11-19 11:30:40
○ 2017-07-17 19:05:14
○ 2026-07-25 16:34:36
NSns4.hayazg.net2015-09-01 → 2016-11-19 · 4 obs
● 2015-09-01 13:46:38
● 2016-11-19 11:30:40
○ 2017-07-17 19:05:14
○ 2026-07-25 16:34:36
MXalt1.aspmx.l.google.com2015-09-01 → 2016-11-19 · 4 obs
● 2015-09-01 13:46:38
● 2016-11-19 11:30:40
○ 2017-07-17 19:05:14
○ 2026-07-25 16:34:36
MXalt2.aspmx.l.google.com2015-09-01 → 2016-11-19 · 4 obs
● 2015-09-01 13:46:38
● 2016-11-19 11:30:40
○ 2017-07-17 19:05:14
○ 2026-07-25 16:34:36
MXaspmx.l.google.com2015-09-01 → 2016-11-19 · 4 obs
● 2015-09-01 13:46:38
● 2016-11-19 11:30:40
○ 2017-07-17 19:05:14
○ 2026-07-25 16:34:36
MXaspmx2.googlemail.com2015-09-01 → 2016-11-19 · 4 obs
● 2015-09-01 13:46:38
● 2016-11-19 11:30:40
○ 2017-07-17 19:05:14
○ 2026-07-25 16:34:36
MXaspmx3.googlemail.com2015-09-01 → 2016-11-19 · 4 obs
● 2015-09-01 13:46:38
● 2016-11-19 11:30:40
○ 2017-07-17 19:05:14
○ 2026-07-25 16:34:36
MXaspmx4.googlemail.com2015-09-01 → 2016-11-19 · 4 obs
● 2015-09-01 13:46:38
● 2016-11-19 11:30:40
○ 2017-07-17 19:05:14
○ 2026-07-25 16:34:36
MXaspmx5.googlemail.com2015-09-01 → 2016-11-19 · 4 obs
● 2015-09-01 13:46:38
● 2016-11-19 11:30:40
○ 2017-07-17 19:05:14
○ 2026-07-25 16:34:36
MXmx.yandex.net2017-07-17 → 2026-07-25 · 6 obs
○ 2016-11-19 11:30:40
● 2017-07-17 19:05:14
● 2026-05-21 18:50:48
○ 2026-06-29 03:56:40
● 2026-07-15 11:05:34
● 2026-07-25 16:34:36
A116.202.249.2322026-02-16 → 2026-07-25 · 2 obs
○ 2026-02-16 13:10:22
○ 2026-07-25 16:34:36
A144.76.114.2422017-07-17 → 2017-07-17 · 4 obs
○ 2016-11-19 11:30:40
● 2017-07-17 19:05:14
○ 2026-02-16 13:10:22
○ 2026-07-25 16:34:36
A5.9.161.2112015-09-01 → 2016-02-11 · 4 obs
● 2015-09-01 13:46:38
● 2016-02-11 02:37:56
○ 2016-05-29 21:03:46
○ 2026-07-25 16:34:36
A82.112.189.2272016-05-29 → 2016-11-19 · 5 obs
○ 2016-02-11 02:37:56
● 2016-05-29 21:03:46
● 2016-11-19 11:30:40
○ 2017-07-17 19:05:14
○ 2026-07-25 16:34:36
A89.104.94.1252026-02-16 → 2026-07-25 · 3 obs
○ 2017-07-17 19:05:14
● 2026-02-16 13:10:22
● 2026-07-25 16:34:36

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
sub.dns.ripn.net, f.dns.ripn.net, a.dns.ripn.net, d.dns.ripn.net...-
fork.sudns1.yandex.net, dns2.yandex.net-

✅ Authoritative Response

Server:213.180.204.213

NS records: dns1.yandex.net, dns2.yandex.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for fork.su (unsigned zone)

⏱️ Timing

Total: 2328ms | Queries: -

📄 Records

TypeCountSample Data
A189.104.94.125
NS2dns2.yandex.net, dns1.yandex.net
MX1mx.yandex.net (pri: 10)
TXT1v=spf1 ip4:82.146.63.205 include:_spf.ya
SOA1dns1.yandex.net dns-hosting.yandex.ru

Analysis

Hierarchy

fork.su serves as the parent of www.fork.su.

IP Addresses

fork.su resolves to one IP address: 89.104.94.125.

Additional host names — including www.fork.su and 89-104-94-125.cloudvps.regruhosting.ru — share IP numbers with fork.su.

Name Servers

fork.su has two authoritative name servers — dns1.yandex.net and dns2.yandex.net.

fork.su uses the same name servers as several other domains — among them marksoft.ru, mbereg.ru, ic-lsk.ru and two more.

fork.su has at least partial name server overlap with other domains, such as fetkulova.ru, faromder.org, soroejka.ru and two others.

It is common to see these name servers used together with name servers dns1.yandex.ru and dns2.yandex.ru.

Both dns1.yandex.net and dns2.yandex.net have two IP addresses each. dns1.yandex.net resolves to 213.180.204.213 and 2a02:6b8::213; dns2.yandex.net resolves to 93.158.134.213 and 2a02:6b8:0:1::213.

Mail Servers

Mail for fork.su is handled by a single mail server, mx.yandex.net.

fork.su uses an identical mail server configuration to several other domains — among them zoya.ru, apm-chel.ru, drzeytin.com and two more.

fork.su has at least partial mail server overlap with other domains such as lalelokantasi.com, vseicrazy.ru, prof-comp.ru and two more.

mx.yandex.net has two IP addresses: 77.88.21.249 and 2a02:6b8::311.