`bilygo.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3031::ac43:d844^{Cloudflare2606:4700:3031::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3032::6815:10e0^{Cloudflare2606:4700:3032::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.16.224^{Cloudflare104.21.16.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.216.68^{Cloudflare172.67.208.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`destiny.ns.cloudflare.com` ⭐
NS	`luke.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	`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`
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`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4	104.21.16.224, 172.67.216.68
		IPv6	2606:4700:3031::ac43:d844, 2606:4700:3032::6815:10e0
SOA	`destiny.ns.cloudflare.com`dns@cloudflare.com serial=2398874646

`com`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.gtld-servers.net` ⭐
	NS	`b.gtld-servers.net`
	NS	`c.gtld-servers.net`
	NS	`d.gtld-servers.net`
	NS	`e.gtld-servers.net`
	NS	`f.gtld-servers.net`
	NS	`g.gtld-servers.net`
	NS	`h.gtld-servers.net`
	NS	`i.gtld-servers.net`
	NS	`j.gtld-servers.net`
	NS	`k.gtld-servers.net`
	NS	`l.gtld-servers.net`
	NS	`m.gtld-servers.net`
	SOA	`a.gtld-servers.net`nstld@verisign-grs.com serial=1774664172

Previously NS for

bilygo.com

Same first word

bilygo.com

Similar names

globiy.com

ygboli.com

golybi.com

blogyi.com

biogly.com

gilboy.com.au

biolgy.com

ligboy.org

DNS History

15 records (9 active, 6 former)

○NSbilygo.com2016-07-10 → 2020-01-22 · 4 obs

● 2016-07-10 15:41:20
● 2020-01-22 13:27:06
○ 2026-02-18 08:15:52
○ 2026-03-28 02:18:38

●NSdestiny.ns.cloudflare.com2026-02-18 → 2026-03-28 · 3 obs

○ 2020-01-22 13:27:06
● 2026-02-18 08:15:52
● 2026-03-28 02:18:38

●NSluke.ns.cloudflare.com2026-02-18 → 2026-03-28 · 3 obs

○ 2020-01-22 13:27:06
● 2026-02-18 08:15:52
● 2026-03-28 02:18:38

○NSns1.cafe24.co.kr2016-07-10 → 2020-01-22 · 4 obs

● 2016-07-10 15:41:20
● 2020-01-22 13:27:06
○ 2026-02-18 08:15:52
○ 2026-03-28 02:18:38

○NSns1.cafe24.com2016-07-10 → 2020-01-22 · 4 obs

● 2016-07-10 15:41:20
● 2020-01-22 13:27:06
○ 2026-02-18 08:15:52
○ 2026-03-28 02:18:38

○NSns2.cafe24.co.kr2016-07-10 → 2020-01-22 · 4 obs

● 2016-07-10 15:41:20
● 2020-01-22 13:27:06
○ 2026-02-18 08:15:52
○ 2026-03-28 02:18:38

○NSns2.cafe24.com2016-07-10 → 2020-01-22 · 4 obs

● 2016-07-10 15:41:20
● 2020-01-22 13:27:06
○ 2026-02-18 08:15:52
○ 2026-03-28 02:18:38

●MXroute1.mx.cloudflare.net2026-02-18 → 2026-03-28 · 2 obs

● 2026-02-18 08:15:52
● 2026-03-28 02:18:38

●MXroute2.mx.cloudflare.net2026-02-18 → 2026-03-28 · 2 obs

● 2026-02-18 08:15:52
● 2026-03-28 02:18:38

●MXroute3.mx.cloudflare.net2026-02-18 → 2026-03-28 · 2 obs

● 2026-02-18 08:15:52
● 2026-03-28 02:18:38

●A104.21.16.2242026-02-18 → 2026-03-28 · 3 obs

○ 2020-01-22 13:27:06
● 2026-02-18 08:15:52
● 2026-03-28 02:18:38

○A112.175.45.502016-07-10 → 2020-01-22 · 4 obs

● 2016-07-10 15:41:20
● 2020-01-22 13:27:06
○ 2026-02-18 08:15:52
○ 2026-03-28 02:18:38

●A172.67.216.682026-02-18 → 2026-03-28 · 3 obs

○ 2020-01-22 13:27:06
● 2026-02-18 08:15:52
● 2026-03-28 02:18:38

●A2606:4700:3031::ac43:d8442026-02-18 → 2026-03-28 · 3 obs

○ 2020-01-22 13:27:06
● 2026-02-18 08:15:52
● 2026-03-28 02:18:38

●A2606:4700:3032::6815:10e02026-02-18 → 2026-03-28 · 3 obs

○ 2020-01-22 13:27:06
● 2026-02-18 08:15:52
● 2026-03-28 02:18:38

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	b.gtld-servers.net, a.gtld-servers.net, c.gtld-servers.net, j.gtld-servers.net...	-
bilygo.com	luke.ns.cloudflare.com, destiny.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.194.76

NS records: luke.ns.cloudflare.com, destiny.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bilygo.com (unsigned zone)

⏱️ Timing

Total: 4188ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.16.224, 172.67.216.68`
AAAA	2	`2606:4700:3032::6815:10e0, 2606:4700:3031::ac43:d844`
NS	2	`destiny.ns.cloudflare.com, luke.ns.cloudflare.com`
MX	3	`route1.mx.cloudflare.net (pri: 26), route3.mx.cloudflare.net (pri: 55)...`
TXT	1	`v=spf1 include:_spf.mx.cloudflare.net ~a`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`destiny.ns.cloudflare.com dns.cloudflare`

📌 Glue Records Collected

Total: 12

Out-of-bailiwick: 12 (luke.ns.cloudflare.com, luke.ns.cloudflare.com, luke.ns.cloudflare.com...)

Analysis

IP Addresses

Four IP numbers are pointed to by bilygo.com: 2606:4700:3031::ac43:d844, 2606:4700:3032::6815:10e0, 104.21.16.224 and 172.67.216.68.

Name Servers

bilygo.com is delegated to two name servers destiny.ns.cloudflare.com and luke.ns.cloudflare.com.

Mail Servers

bilygo.com is handled by three mail servers: route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

Host names with six IP numbers:

route1.mx.cloudflare.net points to: 2606:4700:f5::b, 2606:4700:f5::c, 2606:4700:f5::d, 162.159.205.11, 162.159.205.12 and 162.159.205.13.

route2.mx.cloudflare.net points to: 2606:4700:f5::e, 2606:4700:f5::f, 2606:4700:f5::10, 162.159.205.17, 162.159.205.18 and 162.159.205.19.

route3.mx.cloudflare.net points to: 2606:4700:f5::11, 2606:4700:f5::12, 2606:4700:f5::13, 162.159.205.23, 162.159.205.24 and 162.159.205.25.

bilygo.com - robtex.com

bilygo.com

com

Previously NS for

Same first word

Similar names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

IP Addresses

Name Servers

Mail Servers

`bilygo.com`

`com`