belaba.com - dns.ninja

`belaba.com`

DNSSEC	⚠️ Not signed
A	54.215.31.113^{🇺🇸 Amazon54.215.0.0/17 EC2 SFO prefix}
		PTR	`ec2-54-215-31-113.us-west-1.compute.amazonaws.com`
NS	`ns1.dyna-ns.net` ⭐
		A	2400:cb00:2049:1::a29f:1a5c^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	2400:cb00:2049:1::a29f:1b9e^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.26.92^{Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.dyna-ns.net`
		A	162.159.27.158^{Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.dyna-ns.net`
NS	`ns2.dyna-ns.net`
		A	2400:cb00:2049:1::a29f:1805^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	2400:cb00:2049:1::a29f:1905^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.24.5^{Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.dyna-ns.net`
		A	162.159.25.5^{Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.dyna-ns.net`
SOA	`ns1.dyna-ns.net`hostmaster@belaba.com 2026-06-27 #2

`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=1783192046

Same first word

belaba.com

Similar names

elbaba.de

babela.com.cn

baelab.com

baelab.net

babael.com

elbaba.com

elbaba.org

bealab.ru

babela.cg

bealab.com

baabel.ro

baabel.co

baabel.com

ababel.com

babela.com

ababel.org

abbeal.com

labeba.com

abelab.de

bebala.de

ababel.de

balabe.com

elbaba.net

DNS History

16 records (3 active, 13 former)

○NSlocalhost2015-08-05 → 2016-01-20 · 4 obs

● 2015-08-05 01:37:00
● 2016-01-20 05:16:20
○ 2016-03-10 02:01:48
○ 2026-07-04 19:19:46

○NSns-es.1and1-dns.biz2016-05-04 → 2017-08-16 · 5 obs

○ 2016-03-10 02:01:48
● 2016-05-04 18:50:54
● 2017-08-16 08:51:18
○ 2026-06-20 00:32:24
○ 2026-07-04 19:19:46

○NSns-es.1and1-dns.com2016-05-04 → 2017-08-16 · 5 obs

○ 2016-03-10 02:01:48
● 2016-05-04 18:50:54
● 2017-08-16 08:51:18
○ 2026-06-20 00:32:24
○ 2026-07-04 19:19:46

○NSns-es.1and1-dns.es2016-05-04 → 2017-08-16 · 5 obs

○ 2016-03-10 02:01:48
● 2016-05-04 18:50:54
● 2017-08-16 08:51:18
○ 2026-06-20 00:32:24
○ 2026-07-04 19:19:46

○NSns-es.1and1-dns.org2016-05-04 → 2017-08-16 · 5 obs

○ 2016-03-10 02:01:48
● 2016-05-04 18:50:54
● 2017-08-16 08:51:18
○ 2026-06-20 00:32:24
○ 2026-07-04 19:19:46

●NSns1.dyna-ns.net2026-06-20 → 2026-07-04 · 3 obs

○ 2017-08-16 08:51:18
● 2026-06-20 00:32:24
● 2026-07-04 19:19:46

○NSns1.mytrafficmanagement.com2015-08-05 → 2016-01-20 · 4 obs

● 2015-08-05 01:37:00
● 2016-01-20 05:16:20
○ 2016-03-10 02:01:48
○ 2026-07-04 19:19:46

●NSns2.dyna-ns.net2026-06-20 → 2026-07-04 · 3 obs

○ 2017-08-16 08:51:18
● 2026-06-20 00:32:24
● 2026-07-04 19:19:46

○NSns2.mytrafficmanagement.com2015-08-05 → 2016-01-20 · 4 obs

● 2015-08-05 01:37:00
● 2016-01-20 05:16:20
○ 2016-03-10 02:01:48
○ 2026-07-04 19:19:46

○MXmail.mxproc.com2015-08-05 → 2016-01-20 · 4 obs

● 2015-08-05 01:37:00
● 2016-01-20 05:16:20
○ 2016-03-10 02:01:48
○ 2026-07-04 19:19:46

○MXmx00.1and1.es2016-05-04 → 2017-08-16 · 5 obs

○ 2016-03-10 02:01:48
● 2016-05-04 18:50:54
● 2017-08-16 08:51:18
○ 2026-06-20 00:32:24
○ 2026-07-04 19:19:46

○MXmx01.1and1.es2016-05-04 → 2017-08-16 · 5 obs

○ 2016-03-10 02:01:48
● 2016-05-04 18:50:54
● 2017-08-16 08:51:18
○ 2026-06-20 00:32:24
○ 2026-07-04 19:19:46

○A2001:8d8:1001:41f8:b59e:226d:2968:983f2016-05-04 → 2017-08-16 · 5 obs

○ 2016-03-10 02:01:48
● 2016-05-04 18:50:54
● 2017-08-16 08:51:18
○ 2026-06-20 00:32:24
○ 2026-07-04 19:19:46

○A217.160.230.1662016-05-04 → 2017-08-16 · 5 obs

○ 2016-03-10 02:01:48
● 2016-05-04 18:50:54
● 2017-08-16 08:51:18
○ 2026-06-20 00:32:24
○ 2026-07-04 19:19:46

○A50.56.218.1892015-08-05 → 2016-01-20 · 4 obs

● 2015-08-05 01:37:00
● 2016-01-20 05:16:20
○ 2016-03-10 02:01:48
○ 2026-07-04 19:19:46

●A54.215.31.1132026-06-20 → 2026-07-04 · 3 obs

○ 2017-08-16 08:51:18
● 2026-06-20 00:32:24
● 2026-07-04 19:19:46

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
belaba.com	ns2.dyna-ns.net, ns1.dyna-ns.net	-

✅ Authoritative Response

Server:162.159.27.158

NS records: ns2.dyna-ns.net, ns1.dyna-ns.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for belaba.com (unsigned zone)

⏱️ Timing

Total: 241ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`54.215.31.113`
NS	2	`ns1.dyna-ns.net, ns2.dyna-ns.net`
SOA	1	`ns1.dyna-ns.net hostmaster.belaba.com`

Analysis

IP Addresses

belaba.com points to a single IP number: 54.215.31.113.

Additional host names — thepetvault.com, flyfishingshirts.com, 4see.net and two others — share IP numbers with belaba.com.

Name Servers

belaba.com uses two name servers for its delegation: ns1.dyna-ns.net and ns2.dyna-ns.net.

belaba.com shares its name server setup with other domains, including 0p0p.sbs, vegasarena.de, vparking.net and two others.

Hosts ns1.dyna-ns.net and ns2.dyna-ns.net each point to four IP addresses: ns1.dyna-ns.net resolves to 162.159.26.92, 162.159.27.158, 2400:cb00:2049:1::a29f:1a5c and 2400:cb00:2049:1::a29f:1b9e, and ns2.dyna-ns.net resolves to 162.159.24.5, 162.159.25.5, 2400:cb00:2049:1::a29f:1805 and 2400:cb00:2049:1::a29f:1905.