`blushly.chat`

DNSSEC	⚠️ Not signed
A	2606:4700:3031::ac43:bbb8^{🇺🇸 Cloudflare2606:4700:3031::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3037::6815:3c13^{🇺🇸 Cloudflare2606:4700:3037::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.60.19^{Cloudflare104.21.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.187.184^{🇺🇸 Cloudflare172.67.176.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`nadia.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3acf^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`nadia.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c0cf^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`nadia.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:20cf^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`nadia.ns.cloudflare.com`
		A	108.162.192.207^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`nadia.ns.cloudflare.com`
		A	172.64.32.207^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`nadia.ns.cloudflare.com`
		A	173.245.58.207^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`nadia.ns.cloudflare.com`
NS	`rex.ns.cloudflare.com`
		A	2606:4700:58::a29f:2c0d^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`rex.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c30d^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`rex.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:230d^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`rex.ns.cloudflare.com`
		A	108.162.195.13^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`rex.ns.cloudflare.com`
		A	162.159.44.13^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`rex.ns.cloudflare.com`
		A	172.64.35.13^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`rex.ns.cloudflare.com`
MX	`mx1.larksuite.com` ⭐
		A	18.139.153.173^{🇸🇬 Amazon18.138.0.0/15 EC2 SIN prefix}
			PTR	`ec2-18-139-153-173.ap-southeast-1.compute.amazonaws.com`
MX	`mx2.larksuite.com`⁽⁵⁾
		A	18.139.153.173^{🇸🇬 Amazon18.138.0.0/15 EC2 SIN prefix}
			PTR	`ec2-18-139-153-173.ap-southeast-1.compute.amazonaws.com`
MX	`mx3.larksuite.com`⁽¹⁰⁾
		A	18.139.153.173^{🇸🇬 Amazon18.138.0.0/15 EC2 SIN prefix}
			PTR	`ec2-18-139-153-173.ap-southeast-1.compute.amazonaws.com`
		A	101.126.58.223^{🇨🇳 VOLCANO-ENGINE101.126.56.0/21 China Internet Network Information Center Floor1, Building No.1 C/-Chinese Academy of Sciences 4, South 4th Street Haidian District,}
		A	122.14.230.154^{🇨🇳 CHINAMOBILE-CN122.14.224.0/20}
TXT	`v=spf1 +include:spf.onlarksuite.com -all`
TXT	`verification-code-site-App_lark=5uTJJC4jn0xpHJLWbPCZ`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.60.19, 172.67.187.184
		IPv6 hints	2606:4700:3031::ac43:bbb8, 2606:4700:3037::6815:3c13
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=43, name=cloudflare-ech.com
SOA	`nadia.ns.cloudflare.com`dns@cloudflare.com serial=2401129689

`chat`

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

Subdomains

static.blushly.chat

Same first word

blushly.chat

DNS History

9 records (9 active, 0 former)

●NSnadia.ns.cloudflare.com2026-04-25 → 2026-05-12 · 2 obs

● 2026-04-25 07:05:38
● 2026-05-12 20:25:46

●NSrex.ns.cloudflare.com2026-04-25 → 2026-05-12 · 2 obs

● 2026-04-25 07:05:38
● 2026-05-12 20:25:46

●MXmx1.larksuite.com2026-04-25 → 2026-05-12 · 2 obs

● 2026-04-25 07:05:38
● 2026-05-12 20:25:46

●MXmx2.larksuite.com2026-04-25 → 2026-05-12 · 2 obs

● 2026-04-25 07:05:38
● 2026-05-12 20:25:46

●MXmx3.larksuite.com2026-04-25 → 2026-05-12 · 2 obs

● 2026-04-25 07:05:38
● 2026-05-12 20:25:46

●A104.21.60.192026-04-25 → 2026-05-12 · 2 obs

● 2026-04-25 07:05:38
● 2026-05-12 20:25:46

●A172.67.187.1842026-04-25 → 2026-05-12 · 2 obs

● 2026-04-25 07:05:38
● 2026-05-12 20:25:46

●A2606:4700:3031::ac43:bbb82026-04-25 → 2026-05-12 · 2 obs

● 2026-04-25 07:05:38
● 2026-05-12 20:25:46

●A2606:4700:3037::6815:3c132026-04-25 → 2026-05-12 · 2 obs

● 2026-04-25 07:05:38
● 2026-05-12 20:25:46

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
chat	v0n1.nic.chat, v0n3.nic.chat, v2n1.nic.chat, v2n0.nic.chat...	12 records
blushly.chat	rex.ns.cloudflare.com, nadia.ns.cloudflare.com	-

✅ Authoritative Response

Server:108.162.195.13

NS records: rex.ns.cloudflare.com, nadia.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for blushly.chat (unsigned zone)

⏱️ Timing

Total: 618ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.187.184, 104.21.60.19`
AAAA	2	`2606:4700:3031::ac43:bbb8, 2606:4700:3037::6815:3c13`
NS	2	`nadia.ns.cloudflare.com, rex.ns.cloudflare.com`
MX	3	`mx1.larksuite.com (pri: 1), mx3.larksuite.com (pri: 10)...`
TXT	2	`v=spf1 +include:spf.onlarksuite.com -all, verification-code-site-App_lark=5uTJJC4j`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`nadia.ns.cloudflare.com dns.cloudflare.c`

📌 Glue Records Collected

Total: 12

In-bailiwick: 12 (v2n1.nic.chat, v2n0.nic.chat, v0n3.nic.chat...)

Analysis

Hierarchy

The parent of static.blushly.chat is blushly.chat.

IP Addresses

blushly.chat maps to four IP numbers: 2606:4700:3031::ac43:bbb8, 2606:4700:3037::6815:3c13, 104.21.60.19 and 172.67.187.184.

other host names include singledate24.com, bergischvalley.de, turklife.com, d.dark2web.top and www.agreco.gr; they share IP numbers with blushly.chat.

Name Servers

Two name servers nadia.ns.cloudflare.com and rex.ns.cloudflare.com handle the delegation for blushly.chat.

blushly.chat shares the same name server setup as other domains, for instance kremenchug.net, xgfchjkghfdrt.pages.dev, lifebloomer.com, choraphor.com and provider3.com.

blushly.chat at least partially shares name servers with other domains, for instance nekoslot-88.shop, spbogoal.xyz, dorivanthesul.com, f9gzm.top and kutcudon.ac.th.

These name servers are commonly used alongside heather.ns.cloudflare.com, dakota.ns.cloudflare.com and ligia.ns.cloudflare.com.

Six IP addresses per host:

nadia.ns.cloudflare.com points to 2606:4700:50::adf5:3acf, 2803:f800:50::6ca2:c0cf, 2a06:98c1:50::ac40:20cf, 108.162.192.207, 172.64.32.207 and 173.245.58.207; rex.ns.cloudflare.com points to 2606:4700:58::a29f:2c0d, 2803:f800:50::6ca2:c30d, 2a06:98c1:50::ac40:230d, 108.162.195.13, 162.159.44.13 and 172.64.35.13

Mail Servers

Three mail servers handle blushly.chat: mx1.larksuite.com, mx2.larksuite.com and mx3.larksuite.com.

blushly.chat shares at least partially some mail servers with other domains, for instance zetamail.vn, netroby.com, corostw.com, didong7.vn and aoutour.com.

Host names with three IP numbers:

mx3.larksuite.com points to: 18.139.153.173, 101.126.58.223 and 122.14.230.154

Host names with one IP number:

mx1.larksuite.com points to: 18.139.153.173

mx2.larksuite.com points to: 18.139.153.173

Host names pointing to 18.139.153.173: mx3.larksuite.com, mx1.larksuite.com and mx2.larksuite.com

blushly.chat - robtex.com

blushly.chat

chat

Subdomains

Same first word

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

Hierarchy

IP Addresses

Name Servers

Mail Servers

`blushly.chat`

`chat`