`bleeping.ai`

DNSSEC	⚠️ Not signed
A	2606:4700:3030::6815:43c4^{🇺🇸 Cloudflare2606:4700:3030::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3034::ac43:b424^{🇺🇸 Cloudflare2606:4700:3034::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.67.196^{Cloudflare104.21.64.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.180.36^{🇺🇸 Cloudflare172.67.176.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`harley.ns.cloudflare.com` ⭐
		A	2606:4700:58::a29f:2c80^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`harley.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c380^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`harley.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2380^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`harley.ns.cloudflare.com`
		A	108.162.195.128^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`harley.ns.cloudflare.com`
		A	162.159.44.128^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`harley.ns.cloudflare.com`
		A	172.64.35.128^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`harley.ns.cloudflare.com`
NS	`sandy.ns.cloudflare.com`
		A	2606:4700:50::adf5:3adb^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`sandy.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c0db^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`sandy.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:20db^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`sandy.ns.cloudflare.com`
		A	108.162.192.219^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`sandy.ns.cloudflare.com`
		A	172.64.32.219^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`sandy.ns.cloudflare.com`
		A	173.245.58.219^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`sandy.ns.cloudflare.com`
MX	`route1.mx.cloudflare.net` ⭐
		A	2606:4700:f5::b^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::c^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::d^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.11^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.12^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.13^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
MX	`route2.mx.cloudflare.net`⁽⁹⁷⁾
		A	2606:4700:f5::e^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::f^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::10^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.17^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.18^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.19^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
MX	`route3.mx.cloudflare.net`⁽¹⁰⁰⁾
		A	2606:4700:f5::11^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::12^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::13^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.23^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.24^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.25^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
TXT	`195ebdaad7fde3118bca64571b1a4c8ae41e3f83`
TXT	`afternic-verification-SAH4cYpQzmdG46dKbZZ6sz`
TXT	`b67bf8ee08c542ffcad9252db9d8129754bd1ed6`
TXT	`google-site-verification=4JqquhtQk7LPU9FOY_5o_nLYGVC-Ql_gFEmuscHgWCY`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.67.196, 172.67.180.36
		IPv6 hints	2606:4700:3030::6815:43c4, 2606:4700:3034::ac43:b424
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=231, name=cloudflare-ech.com
SOA	`harley.ns.cloudflare.com`dns@cloudflare.com serial=2412034821

`ai`

	DNSSEC	🔒 Signed (DS record present)
	NS	`v0n0.nic.ai` ⭐
	NS	`v0n1.nic.ai`
	NS	`v0n2.nic.ai`
	NS	`v0n3.nic.ai`
	NS	`v2n0.nic.ai`
	NS	`v2n1.nic.ai`
	SOA	`v0n0.nic.ai`hostmaster@donuts.email serial=1786643670

Same first word

bleeping.net

bleeping.ai

DNS History

9 records (9 active, 0 former)

●NSharley.ns.cloudflare.com2026-08-06 → 2026-08-13 · 2 obs

● 2026-08-06 16:08:08
● 2026-08-13 17:56:22

●NSsandy.ns.cloudflare.com2026-08-06 → 2026-08-13 · 2 obs

● 2026-08-06 16:08:08
● 2026-08-13 17:56:22

●MXroute1.mx.cloudflare.net2026-08-06 → 2026-08-13 · 2 obs

● 2026-08-06 16:08:08
● 2026-08-13 17:56:22

●MXroute2.mx.cloudflare.net2026-08-06 → 2026-08-13 · 2 obs

● 2026-08-06 16:08:08
● 2026-08-13 17:56:22

●MXroute3.mx.cloudflare.net2026-08-06 → 2026-08-13 · 2 obs

● 2026-08-06 16:08:08
● 2026-08-13 17:56:22

●A104.21.67.1962026-08-06 → 2026-08-13 · 2 obs

● 2026-08-06 16:08:08
● 2026-08-13 17:56:22

●A172.67.180.362026-08-06 → 2026-08-13 · 2 obs

● 2026-08-06 16:08:08
● 2026-08-13 17:56:22

●A2606:4700:3030::6815:43c42026-08-06 → 2026-08-13 · 2 obs

● 2026-08-06 16:08:08
● 2026-08-13 17:56:22

●A2606:4700:3034::ac43:b4242026-08-06 → 2026-08-13 · 2 obs

● 2026-08-06 16:08:08
● 2026-08-13 17:56:22

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
ai	v2n0.nic.ai, v2n1.nic.ai, v0n2.nic.ai, v0n0.nic.ai...	-
bleeping.ai	sandy.ns.cloudflare.com, harley.ns.cloudflare.com	-

✅ Authoritative Response

Server:162.159.44.128

NS records: sandy.ns.cloudflare.com, harley.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bleeping.ai (unsigned zone)

⏱️ Timing

Total: 516ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.67.196, 172.67.180.36`
AAAA	2	`2606:4700:3034::ac43:b424, 2606:4700:3030::6815:43c4`
NS	2	`harley.ns.cloudflare.com, sandy.ns.cloudflare.com`
MX	3	`route3.mx.cloudflare.net (pri: 100), route1.mx.cloudflare.net (pri: 64)...`
TXT	5	`195ebdaad7fde3118bca64571b1a4c8ae41e3f83, afternic-verification-SAH4cYpQzmdG46dKbZ...`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`harley.ns.cloudflare.com dns.cloudflare.`

Analysis

IP Addresses

bleeping.ai directs to four IP numbers, which are 104.21.67.196, 172.67.180.36, 2606:4700:3030::6815:43c4 and 2606:4700:3034::ac43:b424.

Two other host names, along with lctianyi.cn, e(0x706f726e)er.xlesbianas.net and icmc2022.org, also share IP numbers with bleeping.ai.

Name Servers

Two name servers handle the delegation for bleeping.ai: harley.ns.cloudflare.com and sandy.ns.cloudflare.com.

bleeping.ai shares its NS records with other domains, for example uplevel.ai, blind.ai, autosend.ai and two others.

There is at least partial name server overlap between bleeping.ai and other domains — 534z.com, bdbauru.com.br, cheapfastcourse.com and two more among them.

These name servers tend to appear in combination with the name servers rihana.ns.cloudflare.com, jerry.ns.cloudflare.com, melody.ns.cloudflare.com and ollie.ns.cloudflare.com.

DNS names with 6 IP addresses:

harley.ns.cloudflare.com resolves to 108.162.195.128, 162.159.44.128 and 172.64.35.128 among others, with 3 other IP addresses in total.

sandy.ns.cloudflare.com resolves to 108.162.192.219, 172.64.32.219 and 173.245.58.219 among others, with 3 other IP addresses in total.

Mail Servers

Incoming mail for bleeping.ai is delivered via three mail servers: route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

There is at least a partial MX overlap between bleeping.ai and other domains, including hslgeorgia.com, dialog-dienste.de, coronanepal.live and two others.

DNS names with 6 IP addresses:

route1.mx.cloudflare.net resolves to 162.159.205.11, 162.159.205.12 and 162.159.205.13 among others, with 3 other IP addresses in total.

route2.mx.cloudflare.net resolves to 162.159.205.17, 162.159.205.18 and 162.159.205.19 among others, with 3 other IP addresses in total.

route3.mx.cloudflare.net resolves to 162.159.205.23, 162.159.205.24 and 162.159.205.25 among others, with 3 other IP addresses in total.

bleeping.ai - robtex.com

bleeping.ai

ai

Same first word

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

Analysis

IP Addresses

Name Servers

Mail Servers

`bleeping.ai`

`ai`