`koronadoors.com`

DNSSEC	⚠️ Not signed
A	2a00:f940:2:2:1:1:0:215^{🇷🇺 AS-REGRU2a00:f940:2::/48 Reg.Ru Hosting Route}
A	31.31.196.78^{🇷🇺 AS-REGRU31.31.196.0/24 Reg.Ru}
NS	`server215.hosting.reg.ru` ⭐
		A	31.31.196.78^{🇷🇺 AS-REGRU31.31.196.0/24 Reg.Ru}
			PTR	`server215.hosting.reg.ru`
NS	`ns1.hosting.reg.ru`
		A	31.31.194.245^{🇷🇺 AS-REGRU31.31.194.0/24 Reg.Ru}
			PTR	`ns1.hosting.reg.ru`
		A	31.31.194.251^{🇷🇺 AS-REGRU31.31.194.0/24 Reg.Ru}
			PTR	`ns17-1.hosting.reg.ru`
		A	31.31.196.37^{🇷🇺 AS-REGRU31.31.196.0/24 Reg.Ru}
			PTR	`ns18-2.hosting.reg.ru`
		A	31.31.196.52^{🇷🇺 AS-REGRU31.31.196.0/24 Reg.Ru}
			PTR	`ns1.hosting.reg.ru`
		A	31.31.196.61^{🇷🇺 AS-REGRU31.31.196.0/24 Reg.Ru}
			PTR	`ns30-2.hosting.reg.ru`
		A	31.31.196.180^{🇷🇺 AS-REGRU31.31.196.0/24 Reg.Ru}
			PTR	`ns31-1.hosting.reg.ru`
		A	31.31.198.177^{🇷🇺 AS-REGRU31.31.198.0/24 Reg.Ru}
			PTR	`ns2.hosting.reg.ru`
		A	37.140.192.20^{🇷🇺 AS-REGRU37.140.192.0/24 Reg.Ru}
			PTR	`ns29-1.hosting.reg.ru`
		A	37.140.192.93^{🇷🇺 AS-REGRU37.140.192.0/24 Reg.Ru}
			PTR	`ns32-1.hosting.reg.ru`
		A	37.140.193.121^{🇷🇺 AS-REGRU37.140.193.0/24 Reg.Ru}
			PTR	`ns2.hosting.reg.ru`
		A	37.140.196.144^{🇷🇺 AS-REGRU37.140.196.0/24 Reg.Ru}
			PTR	`ns37-1.hosting.reg.ru`
		A	194.58.91.38^{🇷🇺 AS-REGRU194.58.91.0/24 Reg.Ru}
			PTR	`ns38-1.hosting.reg.ru`
		A	194.67.73.6^{🇷🇺 AS-REGRU194.67.73.0/24 Reg.Ru-M9}
			PTR	`ns33-1.hosting.reg.ru`
		A	194.67.73.9^{🇷🇺 AS-REGRU194.67.73.0/24 Reg.Ru-M9}
			PTR	`ns34-2.hosting.reg.ru`
NS	`ns2.hosting.reg.ru`
		A	31.31.194.244^{🇷🇺 AS-REGRU31.31.194.0/24 Reg.Ru}
			PTR	`ns1.hosting.reg.ru`
		A	31.31.196.34^{🇷🇺 AS-REGRU31.31.196.0/24 Reg.Ru}
			PTR	`ns17-2.hosting.reg.ru`
		A	31.31.196.53^{🇷🇺 AS-REGRU31.31.196.0/24 Reg.Ru}
			PTR	`ns1.hosting.reg.ru`
		A	31.31.196.71^{🇷🇺 AS-REGRU31.31.196.0/24 Reg.Ru}
			PTR	`ns32-2.hosting.reg.ru`
		A	31.31.198.161^{🇷🇺 AS-REGRU31.31.198.0/24 Reg.Ru}
			PTR	`ns29-2.hosting.reg.ru`
		A	31.31.198.178^{🇷🇺 AS-REGRU31.31.198.0/24 Reg.Ru}
			PTR	`ns2.hosting.reg.ru`
		A	37.140.192.31^{🇷🇺 AS-REGRU37.140.192.0/24 Reg.Ru}
			PTR	`ns37-2.hosting.reg.ru`
		A	37.140.192.55^{🇷🇺 AS-REGRU37.140.192.0/24 Reg.Ru}
			PTR	`ns30-1.hosting.reg.ru`
		A	37.140.192.58^{🇷🇺 AS-REGRU37.140.192.0/24 Reg.Ru}
			PTR	`ns18-1.hosting.reg.ru`
		A	37.140.192.160^{🇷🇺 AS-REGRU37.140.192.0/24 Reg.Ru}
			PTR	`ns31-2.hosting.reg.ru`
		A	37.140.193.120^{🇷🇺 AS-REGRU37.140.193.0/24 Reg.Ru}
			PTR	`ns2.hosting.reg.ru`
		A	37.140.194.37^{🇷🇺 AS-REGRU37.140.194.0/24 Reg.Ru}
			PTR	`ns38-2.hosting.reg.ru`
		A	194.67.73.7^{🇷🇺 AS-REGRU194.67.73.0/24 Reg.Ru-M9}
			PTR	`ns33-2.hosting.reg.ru`
		A	194.67.73.8^{🇷🇺 AS-REGRU194.67.73.0/24 Reg.Ru-M9}
			PTR	`ns34-1.hosting.reg.ru`
MX	`mx1.hosting.reg.ru` ⭐
		A	31.31.194.240^{🇷🇺 AS-REGRU31.31.194.0/24 Reg.Ru}
			PTR	`relay.hosting.reg.ru`
		A	31.31.194.241^{🇷🇺 AS-REGRU31.31.194.0/24 Reg.Ru}
			PTR	`relay.hosting.reg.ru`
MX	`mx2.hosting.reg.ru`⁽²⁰⁾
		A	31.31.194.240^{🇷🇺 AS-REGRU31.31.194.0/24 Reg.Ru}
			PTR	`relay.hosting.reg.ru`
		A	31.31.194.241^{🇷🇺 AS-REGRU31.31.194.0/24 Reg.Ru}
			PTR	`relay.hosting.reg.ru`
TXT	`v=spf1 ip4:31.31.196.78 a mx include:_spf.hosting.reg.ru ~all`
SOA	`server215.hosting.reg.ru`support@reg.ru 2022-11-01 #29

`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=1784828387

Same first word

koronadoors.com

DNS History

11 records (7 active, 4 former)

○NSns1.hitfarm.com2008-03-15 → 2008-03-15 · 3 obs

● 2008-03-15 01:11:40
○ 2015-10-24 08:12:30
○ 2026-07-23 18:05:50

●NSns1.hosting.reg.ru2026-02-18 → 2026-07-23 · 3 obs

○ 2015-10-24 08:12:30
● 2026-02-18 10:00:42
● 2026-07-23 18:05:50

○NSns2.hitfarm.com2008-03-15 → 2008-03-15 · 3 obs

● 2008-03-15 01:11:40
○ 2015-10-24 08:12:30
○ 2026-07-23 18:05:50

●NSns2.hosting.reg.ru2026-02-18 → 2026-07-23 · 3 obs

○ 2015-10-24 08:12:30
● 2026-02-18 10:00:42
● 2026-07-23 18:05:50

●NSserver215.hosting.reg.ru2026-02-18 → 2026-07-23 · 3 obs

○ 2015-10-24 08:12:30
● 2026-02-18 10:00:42
● 2026-07-23 18:05:50

●MXmx1.hosting.reg.ru2026-02-18 → 2026-07-23 · 3 obs

○ 2015-10-24 08:12:30
● 2026-02-18 10:00:42
● 2026-07-23 18:05:50

●MXmx2.hosting.reg.ru2026-02-18 → 2026-07-23 · 3 obs

○ 2015-10-24 08:12:30
● 2026-02-18 10:00:42
● 2026-07-23 18:05:50

○MXnullmx.koronadoors.com2008-03-15 → 2008-03-15 · 3 obs

● 2008-03-15 01:11:40
○ 2015-10-24 08:12:30
○ 2026-07-23 18:05:50

○A217.68.70.692008-03-15 → 2008-03-15 · 3 obs

● 2008-03-15 01:11:40
○ 2015-10-24 08:12:30
○ 2026-07-23 18:05:50

●A2a00:f940:2:2:1:1:0:2152026-02-18 → 2026-07-23 · 3 obs

○ 2015-10-24 08:12:30
● 2026-02-18 10:00:42
● 2026-07-23 18:05:50

●A31.31.196.782026-02-18 → 2026-07-23 · 3 obs

○ 2015-10-24 08:12:30
● 2026-02-18 10:00:42
● 2026-07-23 18:05:50

🔍 DNS Trace

📋 Delegation Chain

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

✅ Authoritative Response

Server:31.31.194.245

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for koronadoors.com (unsigned zone)

⏱️ Timing

Total: 802ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`31.31.196.78`
AAAA	1	`2a00:f940:2:2:1:1:0:215`
NS	2	`ns1.hosting.reg.ru, ns2.hosting.reg.ru`
MX	2	`mx1.hosting.reg.ru (pri: 10), mx2.hosting.reg.ru (pri: 20)`
TXT	1	`v=spf1 ip4:31.31.196.78 a mx include:_sp`
SOA	1	`server215.hosting.reg.ru support.reg.ru`

Analysis

IP Addresses

koronadoors.com points to the IP addresses 31.31.196.78 and 2a00:f940:2:2:1:1:0:215

Two other host names, along with sporty.events, mail.letmarket.ru and betagroupp.ru, also share IP numbers with koronadoors.com.

Name Servers

koronadoors.com carries NS records delegating to ns1.hosting.reg.ru, ns2.hosting.reg.ru and server215.hosting.reg.ru.

There is at least partial name server overlap between koronadoors.com and other domains — c1000.ru, potolki-sd.ru, sud-expert.su and two more among them.

These name servers regularly appear alongside server256.hosting.reg.ru, server152.hosting.reg.ru, ns3.hosting.reg.ru and 5 other name servers in NS record sets.

DNS names with 14 IP addresses:

ns1.hosting.reg.ru resolves to 31.31.194.245, 31.31.194.251 and 31.31.196.37 among others, with 11 other IP addresses in total.

ns2.hosting.reg.ru resolves to 31.31.194.244, 31.31.196.34 and 31.31.196.53 among others, with 11 other IP addresses in total.

Host names that point to one IP address:

The hostname server215.hosting.reg.ru resolves to 31.31.196.78.

Mail Servers

koronadoors.com is served by two mail servers, mx1.hosting.reg.ru and mx2.hosting.reg.ru.

Among the domains sharing a mail server setup with koronadoors.com are dobri-nastavnik.ru, russkaz.ru, gamelines.ru and two others.

koronadoors.com uses mail servers that are also used by other domains, including pwh.ru, porsche-car.ru and florada.pro.

mx1.hosting.reg.ru and mx2.hosting.reg.ru each point to two IP numbers — 31.31.194.240 and 31.31.194.241 — making both hosts identical in their DNS resolution.

mx1.hosting.reg.ru along with mx2.hosting.reg.ru each resolve to 31.31.194.240 IP addresses.

mx1.hosting.reg.ru along with mx2.hosting.reg.ru each resolve to 31.31.194.241 IP addresses.

koronadoors.com - robtex.com

koronadoors.com

com

Same first word

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

Analysis

IP Addresses

Name Servers

Mail Servers

`koronadoors.com`

`com`