`pepeconnect.cloud`

DNSSEC	⚠️ Not signed
NS	`ed.ns.cloudflare.com` ⭐
		A	2606:4700:58::adf5:3b6f^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ed.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c16f^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`ed.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:216f^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`ed.ns.cloudflare.com`
		A	108.162.193.111^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ed.ns.cloudflare.com`
		A	172.64.33.111^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ed.ns.cloudflare.com`
		A	173.245.59.111^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ed.ns.cloudflare.com`
NS	`tegan.ns.cloudflare.com`
		A	2606:4700:50::adf5:3ae2^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`tegan.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c0e2^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`tegan.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:20e2^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`tegan.ns.cloudflare.com`
		A	108.162.192.226^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	172.64.32.226^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	173.245.58.226^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
SOA	`ed.ns.cloudflare.com`dns@cloudflare.com serial=2410741429

`cloud`

	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=1785325829

📈 Tranco rank: #272,833

Same first word

pepeconnect.cloud

Similar names

peepconnect.com

DNS History

2 records (2 active, 0 former)

●NSed.ns.cloudflare.com2026-07-12 → 2026-07-29 · 2 obs

● 2026-07-12 02:50:28
● 2026-07-29 12:09:58

●NStegan.ns.cloudflare.com2026-07-12 → 2026-07-29 · 2 obs

● 2026-07-12 02:50:28
● 2026-07-29 12:09:58

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
cloud	ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info	-
pepeconnect.cloud	tegan.ns.cloudflare.com, ed.ns.cloudflare.com	-

✅ Authoritative Response

Server:173.245.58.226

NS records: tegan.ns.cloudflare.com, ed.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for pepeconnect.cloud (unsigned zone)

⏱️ Timing

Total: 368ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`ed.ns.cloudflare.com, tegan.ns.cloudflare.com`
SOA	1	`ed.ns.cloudflare.com dns.cloudflare.com`

Analysis

Name Servers

The NS records for pepeconnect.cloud delegate to ed.ns.cloudflare.com and tegan.ns.cloudflare.com.

pepeconnect.cloud uses the same name servers as several other domains — among them rcscard.com, rcscard.co.uk, hover.camera and two more.

At least some of pepeconnect.cloud's name servers are shared with other domains, for example immo-ascolux.ch, viashopmoda.com.br, wangjian.me and two more.

These name servers tend to be deployed in combination with the name servers mustafa.ns.cloudflare.com and lakas.ns.cloudflare.com.

Hostnames that resolve to 6 IP addresses:

ed.ns.cloudflare.com maps to 108.162.193.111, 172.64.33.111, 173.245.59.111 and 3 additional IP addresses.

tegan.ns.cloudflare.com maps to 108.162.192.226, 172.64.32.226, 173.245.58.226 and 3 additional IP addresses.

pepeconnect.cloud - robtex.com