`vepsesignal.click`

DNSSEC	⚠️ Not signed
NS	`kia.ns.cloudflare.com` ⚠️ Not in zone NS records
		A	2606:4700:50::adf5:3ab3^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kia.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c0b3^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`kia.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:20b3^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`kia.ns.cloudflare.com`
		A	108.162.192.179^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kia.ns.cloudflare.com`
		A	172.64.32.179^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kia.ns.cloudflare.com`
		A	173.245.58.179^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kia.ns.cloudflare.com`
NS	`tom.ns.cloudflare.com` ⚠️ Not in zone NS records
		A	2606:4700:58::adf5:3b93^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`tom.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c193^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`tom.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2193^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`tom.ns.cloudflare.com`
		A	108.162.193.147^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`tom.ns.cloudflare.com`
		A	172.64.33.147^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`tom.ns.cloudflare.com`
		A	173.245.59.147^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`tom.ns.cloudflare.com`

`click`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns01.trs-dns.com` ⭐
	NS	`ns.trs-dns.com`
	NS	`ns01.trs-dns.net`
	NS	`ns10.trs-dns.info`
	NS	`ns10.trs-dns.org`
	SOA	`ns.trs-dns.com`trs-ops@tucows.com serial=1785614443

⚠️ On DNS blocklist: tif
⚠️ On DNS blocklist: spam-tlds

Same first word

vepsesignal.click

DNS History

2 records (2 active, 0 former)

●NSkia.ns.cloudflare.com2026-07-27 → 2026-08-01 · 2 obs

● 2026-07-27 09:31:56
● 2026-08-01 20:45:14

●NStom.ns.cloudflare.com2026-07-27 → 2026-08-01 · 2 obs

● 2026-07-27 09:31:56
● 2026-08-01 20:45:14

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
click	ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info	8 records
vepsesignal.click	kia.ns.cloudflare.com, tom.ns.cloudflare.com	-

✅ Authoritative Response

Server:108.162.193.147

NS records: kia.ns.cloudflare.com, tom.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for vepsesignal.click (unsigned zone)

⏱️ Timing

Total: 304ms | Queries: -

📄 Records

Type	Count	Sample Data

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns01.trs-dns.com, ns01.trs-dns.com, ns01.trs-dns.net...)

Analysis

Name Servers

vepsesignal.click is served by two delegated name servers, kia.ns.cloudflare.com and tom.ns.cloudflare.com.

vepsesignal.click uses the same name servers as several other domains — among them casavesense.click, vacuomeflow.click, levora64partners.digital and two more.

There is at least partial name server overlap between vepsesignal.click and other domains — efin2020.com, byfexue.com, dayak777wedeh.live and two more among them.

These name servers are routinely deployed together with the name servers darwin.ns.cloudflare.com.

Hostnames that resolve to 6 IP addresses:

kia.ns.cloudflare.com carries IP addresses 108.162.192.179, 172.64.32.179 and 173.245.58.179, with 3 other addresses beyond those.

tom.ns.cloudflare.com carries IP addresses 108.162.193.147, 172.64.33.147 and 173.245.59.147, with 3 other addresses beyond those.

vepsesignal.click - robtex.com