idcorner.com - dns.ninja

`idcorner.com`

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`
SOA	`ns1.reg.ru`hostmaster@ns1.reg.ru serial=1712302753

`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.net`nstld@verisign-grs.com serial=1783462586

Same first word

idcorner.web.id

idcorner.org

idcorner.co.id

idcorner.com

Similar names

DNS History

12 records (3 active, 9 former)

○NSns01.one.com2015-07-02 → 2015-07-02 · 3 obs

● 2015-07-02 10:05:00
○ 2015-11-09 10:25:22
○ 2026-07-07 22:21:56

○NSns02.one.com2015-07-02 → 2015-07-02 · 3 obs

● 2015-07-02 10:05:00
○ 2015-11-09 10:25:22
○ 2026-07-07 22:21:56

○NSns1.hosting.reg.ru2016-05-03 → 2017-03-29 · 5 obs

○ 2015-11-09 10:25:22
● 2016-05-03 19:23:40
● 2017-03-29 14:56:40
○ 2026-04-08 16:24:36
○ 2026-07-07 22:21:56

●NSns1.reg.ru2026-04-08 → 2026-07-07 · 3 obs

○ 2017-03-29 14:56:40
● 2026-04-08 16:24:36
● 2026-07-07 22:21:56

○NSns2.hosting.reg.ru2016-05-03 → 2017-03-29 · 5 obs

○ 2015-11-09 10:25:22
● 2016-05-03 19:23:40
● 2017-03-29 14:56:40
○ 2026-04-08 16:24:36
○ 2026-07-07 22:21:56

●NSns2.reg.ru2026-04-08 → 2026-07-07 · 3 obs

○ 2017-03-29 14:56:40
● 2026-04-08 16:24:36
● 2026-07-07 22:21:56

○NSserver59.hosting.reg.ru2016-05-03 → 2017-03-29 · 5 obs

○ 2015-11-09 10:25:22
● 2016-05-03 19:23:40
● 2017-03-29 14:56:40
○ 2026-04-08 16:24:36
○ 2026-07-07 22:21:56

●MXmx.yandex.net2016-05-03 → 2026-07-07 · 3 obs

○ 2015-11-09 10:25:22
● 2016-05-03 19:23:40
● 2026-07-07 22:21:56

○MXmxcluster1.one.com2015-07-02 → 2015-07-02 · 3 obs

● 2015-07-02 10:05:00
○ 2015-11-09 10:25:22
○ 2026-07-07 22:21:56

○MXmxcluster2.one.com2015-07-02 → 2015-07-02 · 3 obs

● 2015-07-02 10:05:00
○ 2015-11-09 10:25:22
○ 2026-07-07 22:21:56

○A37.140.192.1022016-05-03 → 2017-03-29 · 5 obs

○ 2015-11-09 10:25:22
● 2016-05-03 19:23:40
● 2017-03-29 14:56:40
○ 2026-04-08 16:24:36
○ 2026-07-07 22:21:56

○A46.30.212.332015-07-02 → 2015-07-02 · 3 obs

● 2015-07-02 10:05:00
○ 2015-11-09 10:25:22
○ 2026-07-07 22:21:56

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
idcorner.com	ns1.reg.ru, ns2.reg.ru	-

✅ Authoritative Response

Server:176.99.13.11

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for idcorner.com (unsigned zone)

⏱️ Timing

Total: 924ms | Queries: -

📄 Records

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

Analysis

Name Servers

idcorner.com is served by two delegated name servers, ns1.reg.ru and ns2.reg.ru.

idcorner.com shares its name server setup with other domains, including pilka.pro, rentservice.pro, loftspb.ru and two others.

Host names with 10 IP numbers:

ns1.reg.ru carries IP addresses 176.99.13.11, 176.99.13.13 and 176.99.13.15, with 7 other addresses beyond those.

ns2.reg.ru carries IP addresses 176.99.13.12, 176.99.13.14 and 176.99.13.16, with 7 other addresses beyond those.

Mail Servers

idcorner.com has one mail server: mx.yandex.net.

idcorner.com shares the same mail server setup as other domains, including nicomix.ru, hotelizumrud.ru, sofiatravel.uz and two others.

At least some of idcorner.com's mail servers are shared with other domains, among them audiotema.com, logist.ru, hubpro.ru and abbiamo.ru.

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