CF1757314093256-tsm20250907181809

DNSWHOIS.INFO - ticketing.su

Search for IP or hostnames:

ticketing.su checked at 2025-09-08T06:48:13.238Z 584ms 147/147/147 100% R:22

`ticketing.su`

	NS	`ns1.reg.ru`
			A	2a00:f940:9::1:1 ^{🇷🇺 AS-REGRU}
			A	2a00:f940:9::2:1 ^{🇷🇺 AS-REGRU}
			A	176.99.13.11^{🇷🇺 AS-REGRU}
				PTR	`ns1.reg.ru`
			A	176.99.13.13^{🇷🇺 AS-REGRU}
				PTR	`ns1.reg.ru`
			A	176.99.13.15^{🇷🇺 AS-REGRU}
				PTR	`ns1.reg.ru`
			A	176.99.13.17^{🇷🇺 AS-REGRU}
				PTR	`ns1.reg.ru`
			A	194.58.117.11^{🇷🇺 AS-REGRU}
				PTR	`ns1.reg.ru`
			A	194.58.117.13^{🇷🇺 AS-REGRU}
				PTR	`ns1.reg.ru`
			A	194.58.117.15^{🇷🇺 AS-REGRU}
				PTR	`ns1.reg.ru`
			A	194.58.117.17^{🇷🇺 AS-REGRU}
				PTR	`ns1.reg.ru`
	NS	`ns2.reg.ru`
			A	2a00:f940:9::1:2 ^{🇷🇺 AS-REGRU}
			A	2a00:f940:9::2:2 ^{🇷🇺 AS-REGRU}
			A	176.99.13.12^{🇷🇺 AS-REGRU}
				PTR	`ns2.reg.ru`
			A	176.99.13.14^{🇷🇺 AS-REGRU}
				PTR	`ns2.reg.ru`
			A	176.99.13.16^{🇷🇺 AS-REGRU}
				PTR	`ns2.reg.ru`
			A	176.99.13.18^{🇷🇺 AS-REGRU}
				PTR	`ns2.reg.ru`
			A	194.58.117.12^{🇷🇺 AS-REGRU}
				PTR	`ns2.reg.ru`
			A	194.58.117.14^{🇷🇺 AS-REGRU}
				PTR	`ns2.reg.ru`
			A	194.58.117.16^{🇷🇺 AS-REGRU}
				PTR	`ns2.reg.ru`
			A	194.58.117.18^{🇷🇺 AS-REGRU}
				PTR	`ns2.reg.ru`
	MX	`cluster.relay.agava.net`
			A	31.31.194.240^{🇷🇺 AS-REGRU}
				PTR	`relay.hosting.reg.ru`
			A	31.31.194.241^{🇷🇺 AS-REGRU}
				PTR	`relay.hosting.reg.ru`
	A	2a00:f940:2:2:1:4:0:95 ^{🇷🇺 AS-REGRU}
	A	31.31.198.199^{🇷🇺 AS-REGRU}
			PTR	`scp95.hosting.reg.ru`

`su`

	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`

Starts with same word
`ticketing.in`
`ticketing.cf`
`ticketing.com`
`ticketing.rs`
`ticketing.at`
`ticketing.fr`
`ticketing.su`
`ticketing.today`
`ticketing.center`
`ticketing.pl`
`ticketing.me`
`ticketing.com.au`
`ticketing.guru`
`ticketing.ch`
`ticketing.company`
`ticketing.expert`
`ticketing.co`
`ticketing.lt`
`ticketing.us`
`ticketing.be`
`ticketing.cn`
`ticketing.jp`
`ticketing.club`

Starts similarily
`ticketing.fr`
`ticketing.su`
`ticketing.today`
`ticketing.center`
`ticketing.pl`
`ticketing.me`
`ticketing.com.au`
`ticketing.guru`
`ticketing.ch`
`ticketing.company`
`ticketing.expert`
`ticketing.co`
`ticketing.lt`
`ticketing.us`
`ticketing.be`
`kinetictg.com`
`ticketing.cn`
`ticketing.jp`
`ticketing.club`
`ticketing.in`
`ticketing.cf`
`ticketing.com`
`ticketing.rs`
`ticketing.at`

AI analysis

ticketing.su points to two IP numbers: 2a00:f940:2:2:1:4:0:95 and 31.31.198.199.

IP numbers are shared by ticketing.su with other host names like zato-lokomotivny.ru, xn--80akjf6acjc.xn--80adxhks, artem-kashkanov.ru, www.expt.ru, and autosab.ru.

Two name servers, ns1.reg.ru and ns2.reg.ru, are delegated to ticketing.su.

The name server setup of ticketing.su is shared with other domains such as lazerom.ru, tracex.ru, secure-payment.ru, farmaksima.ru, and posudaplanet.su.

Ten IP numbers are pointed to by ns1.reg.ru: 2a00:f940:9::1:1, 2a00:f940:9::2:1, 176.99.13.11, 176.99.13.13, 176.99.13.15, 176.99.13.17, 194.58.117.11, 194.58.117.13, 194.58.117.15, and 194.58.117.17. ns2.reg.ru points to another set of ten IP numbers: 2a00:f940:9::1:2, 2a00:f940:9::2:2, 176.99.13.12, 176.99.13.14, 176.99.13.16, 176.99.13.18, 194.58.117.12, 194.58.117.14, 194.58.117.16, and 194.58.117.18.

The mail server cluster.relay.agava.net is responsible for handling ticketing.su.

Just like the domains avtoarenda.net, brilliance.ru, ntc-eds.ru, 2yy.ru, and kuraaltai.ru, ticketing.su also has the same mail server setup.

Some mail servers are shared, at least partially, by ticketing.su with other domains like chak-avto.ru, ast-nn.ru, frostway.ru, as-print.ru, and churilov.com.

The mail servers mx1.hosting.reg.ru and mx2.hosting.reg.ru are commonly utilized in conjunction with these mail servers.

cluster.relay.agava.net points to two IP numbers: 31.31.194.240 and 31.31.194.241.

dbq

qTqqcIB CF johedugfp 2025-09-08