`cleverwedding.ru`

DNSSEC	⚠️ Not signed
A	92.53.126.118^{🇷🇺 TimeWeb-AS92.53.126.0/24}
		PTR	`vh254.timeweb.ru`
NS	`ns1.timeweb.ru` ⭐
		A	2a03:6f04:dead:bee::1^{🇷🇺 TimeWeb-AS2a03:6f00::/29}
		A	85.193.93.93^{🇵🇱 TimeWeb-AS85.193.93.0/24}
			PTR	`ns1.timeweb.ru`
NS	`ns2.timeweb.ru`
		A	2a03:6f04:dead:bee::2^{🇷🇺 TimeWeb-AS2a03:6f00::/29}
		A	85.193.93.85^{🇵🇱 TimeWeb-AS85.193.93.0/24}
			PTR	`ns2.timeweb.ru`
NS	`ns3.timeweb.org`
		A	2a03:6f07:4::2^{🇷🇺 TimeWeb-AS2a03:6f00::/29}
		A	217.78.234.130^{🇷🇺 TimeWeb-AS217.78.234.0/24}
NS	`ns4.timeweb.org`
		A	2a00:65e0:6:5:232a::2^{🇷🇺 RETNRU-SPB-AS2a00:65e0::/32 CJSC "RetnNet"}
		A	139.45.249.139^{🇷🇺 RETNRU-SPB-AS139.45.248.0/21 RETN-SPB}
			PTR	`gw-139.45.249.139-rt1.km.spb.retn.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.timeweb.ru`dns@timeweb.ru serial=11112024

`ru`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.dns.ripn.net` ⭐
	NS	`b.dns.ripn.net`
	NS	`d.dns.ripn.net`
	NS	`e.dns.ripn.net`
	NS	`f.dns.ripn.net`
	SOA	`a.dns.ripn.net`hostmaster@ripn.net serial=4068846

Same first word

cleverwedding.ru

DNS History

12 records (6 active, 6 former)

●NSns1.timeweb.ru2015-08-20 → 2026-05-12 · 5 obs

● 2015-08-20 03:04:38
○ 2015-12-10 21:45:36
○ 2017-03-18 05:50:00
● 2026-03-16 16:23:42
● 2026-05-12 11:23:06

○NSns1.vigbo.com2015-12-10 → 2017-03-18 · 5 obs

○ 2015-08-20 03:04:38
● 2015-12-10 21:45:36
● 2017-03-18 05:50:00
○ 2026-03-16 16:23:42
○ 2026-05-12 11:23:06

●NSns2.timeweb.ru2015-08-20 → 2026-05-12 · 5 obs

● 2015-08-20 03:04:38
○ 2015-12-10 21:45:36
○ 2017-03-18 05:50:00
● 2026-03-16 16:23:42
● 2026-05-12 11:23:06

○NSns2.vigbo.com2015-12-10 → 2017-03-18 · 5 obs

○ 2015-08-20 03:04:38
● 2015-12-10 21:45:36
● 2017-03-18 05:50:00
○ 2026-03-16 16:23:42
○ 2026-05-12 11:23:06

●NSns3.timeweb.org2015-08-20 → 2026-05-12 · 5 obs

● 2015-08-20 03:04:38
○ 2015-12-10 21:45:36
○ 2017-03-18 05:50:00
● 2026-03-16 16:23:42
● 2026-05-12 11:23:06

●NSns4.timeweb.org2015-08-20 → 2026-05-12 · 5 obs

● 2015-08-20 03:04:38
○ 2015-12-10 21:45:36
○ 2017-03-18 05:50:00
● 2026-03-16 16:23:42
● 2026-05-12 11:23:06

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

○ 2016-03-19 22:01:04
● 2016-07-14 07:29:18
● 2026-05-12 11:23:06

○MXmx1.timeweb.ru2015-08-20 → 2016-03-19 · 4 obs

● 2015-08-20 03:04:38
● 2016-03-19 22:01:04
○ 2016-07-14 07:29:18
○ 2026-05-12 11:23:06

○MXmx2.timeweb.ru2015-08-20 → 2016-03-19 · 4 obs

● 2015-08-20 03:04:38
● 2016-03-19 22:01:04
○ 2016-07-14 07:29:18
○ 2026-05-12 11:23:06

○A148.251.179.1512015-12-10 → 2017-03-18 · 5 obs

○ 2015-08-20 03:04:38
● 2015-12-10 21:45:36
● 2017-03-18 05:50:00
○ 2026-03-16 16:23:42
○ 2026-05-12 11:23:06

○A2a03:6f00:1::5c35:7e762015-08-20 → 2015-08-20 · 3 obs

● 2015-08-20 03:04:38
○ 2015-12-10 21:45:36
○ 2026-05-12 11:23:06

●A92.53.126.1182015-08-20 → 2026-05-12 · 5 obs

● 2015-08-20 03:04:38
○ 2015-12-10 21:45:36
○ 2017-03-18 05:50:00
● 2026-03-16 16:23:42
● 2026-05-12 11:23:06

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
ru	b.dns.ripn.net, f.dns.ripn.net, e.dns.ripn.net, a.dns.ripn.net...	-
cleverwedding.ru	ns1.timeweb.ru, ns2.timeweb.ru, ns3.timeweb.org, ns4.timeweb.org	2 records

✅ Authoritative Response

Server:217.78.234.130

NS records: ns1.timeweb.ru, ns2.timeweb.ru, ns3.timeweb.org, ns4.timeweb.org

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for cleverwedding.ru (unsigned zone)

⏱️ Timing

Total: 741ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`92.53.126.118`
NS	4	`ns1.timeweb.ru, ns3.timeweb.org...`
MX	1	`mx.yandex.net (pri: 10)`
TXT	1	`v=spf1 redirect=_spf.yandex.net`
SOA	1	`ns1.timeweb.ru dns.timeweb.ru`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns2.timeweb.ru, ns1.timeweb.ru)

Analysis

IP Addresses

cleverwedding.ru resolves to a single IP address: 92.53.126.118.

Other host names such as eventsrv.tmweb.ru, assa2as.tmweb.ru and vamdoma.ru share IP numbers with cleverwedding.ru.

Name Servers

cleverwedding.ru is delegated to four name servers: ns3.timeweb.org, ns4.timeweb.org, ns1.timeweb.ru and ns2.timeweb.ru.

cleverwedding.ru at least partially shares name servers with other domains, including e.5.1.1.0.0.0.0.0.0.0.0.0.0.0.0.1.0.0.0.5.0.0.0.0.0.f.6.3.0.a.2.ip6.arpa, tyuz.ru, novostroy29.ru, 80.225.188.in-addr.arpa and 2702.ru.

These name servers are commonly used with ns3.timeweb.ru and ns4.timeweb.ru.

Hosts with two IP numbers:

Host ns3.timeweb.org points to 2a03:6f07:4::2 and 217.78.234.130

Host ns4.timeweb.org points to 2a00:65e0:6:5:232a::2 and 139.45.249.139

Host ns1.timeweb.ru points to 2a03:6f04:dead:bee::1 and 85.193.93.93

Host ns2.timeweb.ru points to 2a03:6f04:dead:bee::2 and 85.193.93.85

Mail Servers

cleverwedding.ru is handled by a single mail server, mx.yandex.net.

cleverwedding.ru shares its mail server setup with other domains, including buffviewer.com, netload.su, wowigs.eu, vektoryapi.com and tvseminary.org.

cleverwedding.ru shares some mail servers with other domains, for instance anglisimo.ru, brtop.ru, vagroup.ru and intensivkurs.by.

mx.yandex.net points to two IPs: 2a02:6b8::311 and 77.88.21.249.

cleverwedding.ru - robtex.com