forcecode.ru - dns.ninja

forcecode.ru

DNSSEC⚠️ Not signed
NSns1.nameself.com ⭐
A2a00:15f8:c001:3::144🇷🇺 MASTERHOST-AS2a00:15f8::/32 .masterhost
A87.242.73.100🇷🇺 MASTERHOST-AS87.242.73.0/24
A88.212.207.45🇷🇺 UNITEDNET88.212.206.0/23 EXEPTO SERVERS PLANT
NSns2.nameself.com
A2a02:2100:e001:4::203🇷🇺 UNITEDNET2a02:2100::/32 United Network LLC
A88.212.208.183🇷🇺 UNITEDNET88.212.208.0/22 EXEPTO SERVERS PLANT
A95.213.146.179🇷🇺 SELECTEL95.213.146.0/24 -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 include:_spf.google.com include:spf.mandrillapp.com include:mailgun.or...
TXTyandex-verification: 27fe07d7d95f35c3
SOAns1.nameself.comsupport@regtime.net serial=1770803405

ru

DNSSEC🔒 Signed (DS record present)
NSa.dns.ripn.net ⭐
NSb.dns.ripn.net
NSc.tld-servers.ru
NSd.dns.ripn.net
NSe.dns.ripn.net
NSf.dns.ripn.net
SOAa.dns.ripn.nethostmaster@ripn.net serial=4069894

Same first word

forcecode.de
forcecode.ru
forcecode.com
forcecode.sk

Similar names

codeforce.com
codeforce.com.br
codeforce.co.nz
decoforce.com
codeforce.nl
codeforce.eu
codeforce.net
codeforce.org
codeforce.de

DNS History

18 records (3 active, 15 former)

20162017201820192020202120222023202420252026NSns1.nameself.comns2.nameself.comns3-l2.nic.runs4-cloud.nic.runs4-l2.nic.runs8-cloud.nic.runs8-l2.nic.ruMXmx.yandex.netalt1.aspmx.l.google.comalt2.aspmx.l.google.comalt3.aspmx.l.google.comalt4.aspmx.l.google.comaspmx.l.google.comaspmx2.googlemail.comaspmx3.googlemail.comaspmx4.googlemail.comaspmx5.googlemail.comA78.47.41.101
●NSns1.nameself.com2015-05-24 → 2026-08-07 · 5 obs
● 2015-05-24 15:10:14
○ 2015-10-12 12:28:26
○ 2017-05-20 06:25:46
● 2026-02-17 00:24:16
● 2026-08-07 01:24:32
●NSns2.nameself.com2015-05-24 → 2026-08-07 · 5 obs
● 2015-05-24 15:10:14
○ 2015-10-12 12:28:26
○ 2017-05-20 06:25:46
● 2026-02-17 00:24:16
● 2026-08-07 01:24:32
○NSns3-l2.nic.ru2015-10-12 → 2017-05-20 · 5 obs
○ 2015-05-24 15:10:14
● 2015-10-12 12:28:26
● 2017-05-20 06:25:46
○ 2026-02-17 00:24:16
○ 2026-08-07 01:24:32
○NSns4-cloud.nic.ru2015-10-12 → 2017-05-20 · 5 obs
○ 2015-05-24 15:10:14
● 2015-10-12 12:28:26
● 2017-05-20 06:25:46
○ 2026-02-17 00:24:16
○ 2026-08-07 01:24:32
○NSns4-l2.nic.ru2015-10-12 → 2017-05-20 · 5 obs
○ 2015-05-24 15:10:14
● 2015-10-12 12:28:26
● 2017-05-20 06:25:46
○ 2026-02-17 00:24:16
○ 2026-08-07 01:24:32
○NSns8-cloud.nic.ru2015-10-12 → 2017-05-20 · 5 obs
○ 2015-05-24 15:10:14
● 2015-10-12 12:28:26
● 2017-05-20 06:25:46
○ 2026-02-17 00:24:16
○ 2026-08-07 01:24:32
○NSns8-l2.nic.ru2015-10-12 → 2017-05-20 · 5 obs
○ 2015-05-24 15:10:14
● 2015-10-12 12:28:26
● 2017-05-20 06:25:46
○ 2026-02-17 00:24:16
○ 2026-08-07 01:24:32
○MXalt1.aspmx.l.google.com2015-05-24 → 2017-05-20 · 4 obs
● 2015-05-24 15:10:14
● 2017-05-20 06:25:46
○ 2026-02-17 00:24:16
○ 2026-08-07 01:24:32
○MXalt2.aspmx.l.google.com2015-05-24 → 2017-05-20 · 4 obs
● 2015-05-24 15:10:14
● 2017-05-20 06:25:46
○ 2026-02-17 00:24:16
○ 2026-08-07 01:24:32
○MXalt3.aspmx.l.google.com2015-10-12 → 2017-05-20 · 5 obs
○ 2015-05-24 15:10:14
● 2015-10-12 12:28:26
● 2017-05-20 06:25:46
○ 2026-02-17 00:24:16
○ 2026-08-07 01:24:32
○MXalt4.aspmx.l.google.com2015-10-12 → 2017-05-20 · 5 obs
○ 2015-05-24 15:10:14
● 2015-10-12 12:28:26
● 2017-05-20 06:25:46
○ 2026-02-17 00:24:16
○ 2026-08-07 01:24:32
○MXaspmx.l.google.com2015-05-24 → 2017-05-20 · 4 obs
● 2015-05-24 15:10:14
● 2017-05-20 06:25:46
○ 2026-02-17 00:24:16
○ 2026-08-07 01:24:32
○MXaspmx2.googlemail.com2015-05-24 → 2017-05-20 · 4 obs
● 2015-05-24 15:10:14
● 2017-05-20 06:25:46
○ 2026-02-17 00:24:16
○ 2026-08-07 01:24:32
○MXaspmx3.googlemail.com2015-05-24 → 2017-05-20 · 4 obs
● 2015-05-24 15:10:14
● 2017-05-20 06:25:46
○ 2026-02-17 00:24:16
○ 2026-08-07 01:24:32
○MXaspmx4.googlemail.com2015-05-24 → 2017-05-20 · 4 obs
● 2015-05-24 15:10:14
● 2017-05-20 06:25:46
○ 2026-02-17 00:24:16
○ 2026-08-07 01:24:32
○MXaspmx5.googlemail.com2015-05-24 → 2017-05-20 · 4 obs
● 2015-05-24 15:10:14
● 2017-05-20 06:25:46
○ 2026-02-17 00:24:16
○ 2026-08-07 01:24:32
●MXmx.yandex.net2026-02-17 → 2026-08-07 · 3 obs
○ 2017-05-20 06:25:46
● 2026-02-17 00:24:16
● 2026-08-07 01:24:32
○A78.47.41.1012015-05-24 → 2026-02-17 · 4 obs
● 2015-05-24 15:10:14
● 2026-02-17 00:24:16
○ 2026-03-27 19:19:18
○ 2026-08-07 01:24:32

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
rub.dns.ripn.net, a.dns.ripn.net, f.dns.ripn.net, e.dns.ripn.net...-
forcecode.runs1.nameself.com, ns2.nameself.com-

✅ Authoritative Response

Server:87.242.73.100

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for forcecode.ru (unsigned zone)

⏱️ Timing

Total: 1230ms | Queries: -

📄 Records

TypeCountSample Data
NS2ns2.nameself.com, ns1.nameself.com
MX1mx.yandex.net (pri: 10)
TXT2yandex-verification: 27fe07d7d95f35c3, v=spf1 include:_spf.google.com include:s
SOA1ns1.nameself.com support.regtime.net

Analysis

Name Servers

DNS delegation for forcecode.ru points to two name servers: ns1.nameself.com and ns2.nameself.com.

forcecode.ru has the same name server delegation as a number of other domains, such as buterok.ru, kino67.ru, kazay.ru and two more.

forcecode.ru has partial name server overlap with other domains, including regtime.net.

The hosts ns1.nameself.com and ns2.nameself.com both resolve to three IP numbers: ns1.nameself.com to 87.242.73.100, 88.212.207.45 and 2a00:15f8:c001:3::144, and ns2.nameself.com to 88.212.208.183, 95.213.146.179 and 2a02:2100:e001:4::203.

Mail Servers

forcecode.ru routes its mail through a single mail server, mx.yandex.net.

forcecode.ru has the same mail server arrangement as a number of other domains, for example bilgisayarkirala.net, buynowpaylater.com.gh, mistra.su and two more.

At least a portion of forcecode.ru's mail servers are shared with other domains, among them granit-pamyati.ru and yedpa.com.tr.

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