rezansky.com - dns.ninja

`rezansky.com`

DNSSEC	⚠️ Not signed
A	2001:19f0:1000:6133:5400:4ff:fe92:4834^{🇺🇸 AS-VULTR2001:19f0:1000::/38 Vultr Assigned Prefix}
		PTR	`rezansky.wpmudev.host`
A	207.148.30.253^{🇺🇸 AS-VULTR207.148.16.0/20 Vultr Assigned Prefix}
NS	`ns1.vultr.com` ⭐
		A	2001:19f0:ccc::1^{🇺🇸 AS-VULTR2001:19f0:ccc::/48 DNS1}
		A	2001:19f0:ccd::1^{🇺🇸 AS-VULTR2001:19f0:ccd::/48 Vultr Assigned Prefix}
			PTR	`ns1.vultr.com`
		A	173.199.96.96^{🇺🇸 AS-VULTR173.199.96.0/24 Vultr Assigned Prefix}
			PTR	`ns1.vultrusercontent.com`
NS	`ns1.wpdns.host`
		A	2001:19f0:ccd::1^{🇺🇸 AS-VULTR2001:19f0:ccd::/48 Vultr Assigned Prefix}
			PTR	`ns1.vultr.com`
		A	173.199.96.96^{🇺🇸 AS-VULTR173.199.96.0/24 Vultr Assigned Prefix}
			PTR	`ns1.vultrusercontent.com`
NS	`ns2.wpdns.host`
		A	2001:19f0:ccd::2^{🇺🇸 AS-VULTR2001:19f0:ccd::/48 Vultr Assigned Prefix}
			PTR	`ns2.vultr.com`
		A	173.199.96.97^{🇺🇸 AS-VULTR173.199.96.0/24 Vultr Assigned Prefix}
			PTR	`ns2.vultrusercontent.com`
NS	`ns3.wpdns.host`
		A	2001:19f0:ccd::1^{🇺🇸 AS-VULTR2001:19f0:ccd::/48 Vultr Assigned Prefix}
			PTR	`ns1.vultr.com`
		A	173.199.96.96^{🇺🇸 AS-VULTR173.199.96.0/24 Vultr Assigned Prefix}
			PTR	`ns1.vultrusercontent.com`
SOA	`ns1.vultr.com`dnsadm@choopa.com serial=0

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

Same first word

rezansky.wpmudev.host

rezansky.com

DNS History

19 records (6 active, 13 former)

○NSns1.bluehost.com2020-02-10 → 2020-02-10 · 4 obs

○ 2015-11-11 15:10:54
● 2020-02-10 07:14:24
○ 2026-03-17 20:45:48
○ 2026-08-05 22:23:06

●NSns1.vultr.com2026-03-17 → 2026-08-05 · 3 obs

○ 2020-02-10 07:14:24
● 2026-03-17 20:45:48
● 2026-08-05 22:23:06

●NSns1.wpdns.host2026-03-17 → 2026-08-05 · 3 obs

○ 2020-02-10 07:14:24
● 2026-03-17 20:45:48
● 2026-08-05 22:23:06

○NSns2.bluehost.com2020-02-10 → 2020-02-10 · 4 obs

○ 2015-11-11 15:10:54
● 2020-02-10 07:14:24
○ 2026-03-17 20:45:48
○ 2026-08-05 22:23:06

●NSns2.wpdns.host2026-03-17 → 2026-08-05 · 3 obs

○ 2020-02-10 07:14:24
● 2026-03-17 20:45:48
● 2026-08-05 22:23:06

●NSns3.wpdns.host2026-03-17 → 2026-08-05 · 3 obs

○ 2020-02-10 07:14:24
● 2026-03-17 20:45:48
● 2026-08-05 22:23:06

○NSyns1.yahoo.com2008-03-16 → 2008-03-16 · 3 obs

● 2008-03-16 04:53:48
○ 2015-11-11 15:10:54
○ 2026-08-05 22:23:06

○NSyns2.yahoo.com2008-03-16 → 2008-03-16 · 3 obs

● 2008-03-16 04:53:48
○ 2015-11-11 15:10:54
○ 2026-08-05 22:23:06

○MXmail.rezansky.com2020-02-10 → 2020-02-10 · 4 obs

○ 2015-11-11 15:10:54
● 2020-02-10 07:14:24
○ 2026-03-17 20:45:48
○ 2026-08-05 22:23:06

○MXmxvm2.mail.yahoo.com2008-03-16 → 2008-03-16 · 3 obs

● 2008-03-16 04:53:48
○ 2015-11-11 15:10:54
○ 2026-08-05 22:23:06

○A162.241.225.2192020-02-10 → 2020-02-10 · 4 obs

○ 2015-11-11 15:10:54
● 2020-02-10 07:14:24
○ 2026-03-17 20:45:48
○ 2026-08-05 22:23:06

●A2001:19f0:1000:6133:5400:4ff:fe92:48342026-03-17 → 2026-08-05 · 3 obs

○ 2020-02-10 07:14:24
● 2026-03-17 20:45:48
● 2026-08-05 22:23:06

●A207.148.30.2532026-03-17 → 2026-08-05 · 3 obs

○ 2020-02-10 07:14:24
● 2026-03-17 20:45:48
● 2026-08-05 22:23:06

○A68.142.234.502008-03-16 → 2008-03-16 · 3 obs

● 2008-03-16 04:53:48
○ 2015-11-11 15:10:54
○ 2026-08-05 22:23:06

○A68.142.234.512008-03-16 → 2008-03-16 · 3 obs

● 2008-03-16 04:53:48
○ 2015-11-11 15:10:54
○ 2026-08-05 22:23:06

○A68.142.234.572008-03-16 → 2008-03-16 · 3 obs

● 2008-03-16 04:53:48
○ 2015-11-11 15:10:54
○ 2026-08-05 22:23:06

○A68.142.234.582008-03-16 → 2008-03-16 · 3 obs

● 2008-03-16 04:53:48
○ 2015-11-11 15:10:54
○ 2026-08-05 22:23:06

○A68.142.234.592008-03-16 → 2008-03-16 · 3 obs

● 2008-03-16 04:53:48
○ 2015-11-11 15:10:54
○ 2026-08-05 22:23:06

○A68.142.234.602008-03-16 → 2008-03-16 · 3 obs

● 2008-03-16 04:53:48
○ 2015-11-11 15:10:54
○ 2026-08-05 22:23:06

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
rezansky.com	ns1.wpdns.host, ns2.wpdns.host, ns3.wpdns.host	-

✅ Authoritative Response

Server:173.199.96.96

NS records: ns1.wpdns.host, ns2.wpdns.host, ns3.wpdns.host

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for rezansky.com (unsigned zone)

⏱️ Timing

Total: 361ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`207.148.30.253`
AAAA	1	`2001:19f0:1000:6133:5400:4ff:fe92:4834`
NS	3	`ns1.wpdns.host, ns2.wpdns.host...`
SOA	1	`ns1.vultr.com dnsadm.choopa.com`

Analysis

IP Addresses

rezansky.com points to the IP addresses 207.148.30.253 and 2001:19f0:1000:6133:5400:4ff:fe92:4834

Other host names share IP numbers with rezansky.com; rezansky.wpmudev.host is one such example.

Name Servers

rezansky.com has four authoritative name servers: ns1.vultr.com, ns1.wpdns.host, ns2.wpdns.host and ns3.wpdns.host.

At least some of rezansky.com's name servers are shared with other domains, for example busydaze.com, knox.city, classauction.com and two more.

These name servers tend to be used in conjunction with the name servers ns2.vultr.com.

Host names with three IP numbers:

ns1.vultr.com resolves to three addresses: 173.199.96.96, 2001:19f0:ccc::1 and 2001:19f0:ccd::1.

Host names with two IP numbers:

ns1.wpdns.host maps to two IP addresses — 173.199.96.96 and 2001:19f0:ccd::1.

ns2.wpdns.host maps to two IP addresses — 173.199.96.97 and 2001:19f0:ccd::2.

ns3.wpdns.host maps to two IP addresses — 173.199.96.96 and 2001:19f0:ccd::1.

ns1.vultr.com, ns1.wpdns.host and ns3.wpdns.host are host names that all point to 2001:19f0:ccd::1.

ns1.vultr.com, ns1.wpdns.host and ns3.wpdns.host are host names that all point to 173.199.96.96.