1cbase.tech - dns.ninja

`1cbase.tech`

DNSSEC	⚠️ Not signed
NS	`ns1.reg.ru` ⭐
		A	2a00:f940:9::1:1^{🇷🇺 AS-REGRU2a00:f940:9::/48 Reg.Ru Hosting}
		A	2a00:f940:9::2:1^{🇷🇺 AS-REGRU2a00:f940:9::/48 Reg.Ru Hosting}
		A	176.99.13.11^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	176.99.13.13^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	176.99.13.15^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	176.99.13.17^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	194.58.117.11^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	194.58.117.13^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	194.58.117.15^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	194.58.117.17^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
NS	`ns2.reg.ru`
		A	2a00:f940:9::1:2^{🇷🇺 AS-REGRU2a00:f940:9::/48 Reg.Ru Hosting}
		A	2a00:f940:9::2:2^{🇷🇺 AS-REGRU2a00:f940:9::/48 Reg.Ru Hosting}
		A	176.99.13.12^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	176.99.13.14^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	176.99.13.16^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	176.99.13.18^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	194.58.117.12^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	194.58.117.14^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	194.58.117.16^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	194.58.117.18^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
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: 2eb7b5c91a1bec7c`
SOA	`ns1.reg.ru`hostmaster@ns1.reg.ru serial=1759901014

`tech`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns01.trs-dns.com` ⭐
	NS	`ns.trs-dns.com`
	NS	`ns01.trs-dns.net`
	NS	`ns10.trs-dns.info`
	NS	`ns10.trs-dns.org`
	SOA	`ns.trs-dns.com`trs-ops@tucows.com serial=1784501644

Same first word

1cbase.ru

1cbase.com

1cbase.tech

DNS History

13 records (3 active, 10 former)

●NSns1.reg.ru2026-03-15 → 2026-07-19 · 3 obs

○ 2020-03-05 06:54:14
● 2026-03-15 00:06:00
● 2026-07-19 23:00:02

●NSns2.reg.ru2026-03-15 → 2026-07-19 · 3 obs

○ 2020-03-05 06:54:14
● 2026-03-15 00:06:00
● 2026-07-19 23:00:02

○NSns29.domaincontrol.com2020-03-05 → 2020-03-05 · 3 obs

● 2020-03-05 06:54:14
○ 2026-03-15 00:06:00
○ 2026-07-19 23:00:02

○NSns30.domaincontrol.com2020-03-05 → 2020-03-05 · 3 obs

● 2020-03-05 06:54:14
○ 2026-03-15 00:06:00
○ 2026-07-19 23:00:02

○MXalt1.aspmx.l.google.com2020-03-05 → 2020-03-05 · 3 obs

● 2020-03-05 06:54:14
○ 2026-03-15 00:06:00
○ 2026-07-19 23:00:02

○MXalt2.aspmx.l.google.com2020-03-05 → 2020-03-05 · 3 obs

● 2020-03-05 06:54:14
○ 2026-03-15 00:06:00
○ 2026-07-19 23:00:02

○MXalt3.aspmx.l.google.com2020-03-05 → 2020-03-05 · 3 obs

● 2020-03-05 06:54:14
○ 2026-03-15 00:06:00
○ 2026-07-19 23:00:02

○MXalt4.aspmx.l.google.com2020-03-05 → 2020-03-05 · 3 obs

● 2020-03-05 06:54:14
○ 2026-03-15 00:06:00
○ 2026-07-19 23:00:02

○MXaspmx.l.google.com2020-03-05 → 2020-03-05 · 3 obs

● 2020-03-05 06:54:14
○ 2026-03-15 00:06:00
○ 2026-07-19 23:00:02

○MXilgntdz55rcryqzssiy2iksz4wi7kzxjzsssuamdipaffwpezejq.mx-verification.google.com2020-03-05 → 2020-03-05 · 3 obs

● 2020-03-05 06:54:14
○ 2026-03-15 00:06:00
○ 2026-07-19 23:00:02

○MXmail.1cbase.tech2020-03-05 → 2020-03-05 · 3 obs

● 2020-03-05 06:54:14
○ 2026-03-15 00:06:00
○ 2026-07-19 23:00:02

●MXmx.yandex.net2026-03-15 → 2026-07-19 · 3 obs

○ 2020-03-05 06:54:14
● 2026-03-15 00:06:00
● 2026-07-19 23:00:02

○A212.109.215.572020-03-05 → 2020-03-05 · 3 obs

● 2020-03-05 06:54:14
○ 2026-03-15 00:06:00
○ 2026-07-19 23:00:02

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
tech	ns10.trs-dns.org, ns10.trs-dns.info, ns01.trs-dns.com, ns01.trs-dns.net	-
1cbase.tech	ns1.reg.ru, ns2.reg.ru	-

✅ Authoritative Response

Server:176.99.13.12

NS records: ns1.reg.ru, ns2.reg.ru

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for 1cbase.tech (unsigned zone)

⏱️ Timing

Total: 898ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`ns1.reg.ru, ns2.reg.ru`
MX	1	`mx.yandex.net (pri: 10)`
TXT	2	`v=spf1 redirect=_spf.yandex.net, yandex-verification: 2eb7b5c91a1bec7c`
SOA	1	`ns1.reg.ru hostmaster.ns1.reg.ru`

Analysis

Name Servers

DNS delegation for 1cbase.tech points to two name servers: ns1.reg.ru and ns2.reg.ru.

1cbase.tech uses the same name servers as several other domains — among them bhdclub.ru, bilinza.ru, kupimed.ru and two more.

Hostnames that resolve to 10 IP addresses:

ns1.reg.ru has IP addresses 176.99.13.11, 176.99.13.13 and 176.99.13.15, plus 7 other.

ns2.reg.ru has IP addresses 176.99.13.12, 176.99.13.14 and 176.99.13.16, plus 7 other.

Mail Servers

Mail for 1cbase.tech is handled by a single mail server, mx.yandex.net.

1cbase.tech uses an identical mail server configuration to several other domains — among them solo-shop.ru, mbatekstil.com.tr, ilovesupersport.com and two more.

1cbase.tech overlaps on mail servers with several other domains, for example threezeta.com, nowayvpn.com, httpro.com and thietkeweb.edu.vn.

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