indobyte.com - dns.ninja

`indobyte.com`

DNSSEC	⚠️ Not signed
A	195.250.26.66^{🇬🇧 WHG-USE1195.250.26.0/24}
		PTR	`s863.use1.mysecurecloudhost.com`
NS	`ns100.webhostingbuzz.com` ⭐
		A	192.243.110.201^{🇬🇧 WHG-USE1192.243.110.0/24}
			PTR	`alphaserver.corewebsitedesign.co.uk`
NS	`ns101.webhostingbuzz.com`
		A	192.250.239.210^{🇬🇧 WHG-LON192.250.239.0/24}
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1f::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`pd-in-f26.1e100.net`
		A	142.250.31.27^{🇺🇸 Google142.250.31.0/24}
			PTR	`bj-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.26^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f26.1e100.net`
MX	`aspmx2.googlemail.com`⁽¹⁰⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.1e100.net`
TXT	`v=spf1 +a +mx +ip4:195.250.26.61 include:spf.mysecurecloudhost.com +ip4:195.2...`
SOA	`ns100.webhostingbuzz.com`servers@mysecurecloudhost.com 2026-05-26 #5

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

Same first word

indobyte.id

indobyte.com

Similar names

DNS History

18 records (6 active, 12 former)

○NSns1.nsresponse.com2016-11-04 → 2016-12-15 · 5 obs

○ 2016-09-10 07:31:50
● 2016-11-04 15:17:44
● 2016-12-15 13:20:20
○ 2026-05-11 06:41:56
○ 2026-06-18 23:57:12

●NSns100.webhostingbuzz.com2026-05-11 → 2026-06-18 · 3 obs

○ 2016-12-15 13:20:20
● 2026-05-11 06:41:56
● 2026-06-18 23:57:12

○NSns100.whbdns.com2008-03-20 → 2016-04-04 · 4 obs

● 2008-03-20 09:29:04
● 2016-04-04 00:23:48
○ 2016-06-21 12:35:56
○ 2026-06-18 23:57:12

●NSns101.webhostingbuzz.com2026-05-11 → 2026-06-18 · 3 obs

○ 2016-12-15 13:20:20
● 2026-05-11 06:41:56
● 2026-06-18 23:57:12

○NSns101.whbdns.com2008-03-20 → 2016-04-04 · 4 obs

● 2008-03-20 09:29:04
● 2016-04-04 00:23:48
○ 2016-06-21 12:35:56
○ 2026-06-18 23:57:12

○NSns17.domaincontrol.com2016-06-21 → 2016-09-10 · 5 obs

○ 2016-04-04 00:23:48
● 2016-06-21 12:35:56
● 2016-09-10 07:31:50
○ 2016-11-04 15:17:44
○ 2026-06-18 23:57:12

○NSns18.domaincontrol.com2016-06-21 → 2016-09-10 · 5 obs

○ 2016-04-04 00:23:48
● 2016-06-21 12:35:56
● 2016-09-10 07:31:50
○ 2016-11-04 15:17:44
○ 2026-06-18 23:57:12

○NSns2.nsresponse.com2016-11-04 → 2016-12-15 · 5 obs

○ 2016-09-10 07:31:50
● 2016-11-04 15:17:44
● 2016-12-15 13:20:20
○ 2026-05-11 06:41:56
○ 2026-06-18 23:57:12

●MXalt1.aspmx.l.google.com2008-03-20 → 2026-06-18 · 2 obs

● 2008-03-20 09:29:04
● 2026-06-18 23:57:12

○MXalt2.aspmx.l.google.com2016-06-21 → 2026-05-13 · 4 obs

○ 2016-04-04 00:23:48
● 2016-06-21 12:35:56
● 2026-05-13 02:27:00
○ 2026-06-18 23:57:12

○MXalt3.aspmx.l.google.com2016-11-04 → 2026-05-13 · 4 obs

○ 2016-06-21 12:35:56
● 2016-11-04 15:17:44
● 2026-05-13 02:27:00
○ 2026-06-18 23:57:12

○MXalt4.aspmx.l.google.com2016-11-04 → 2026-05-13 · 4 obs

○ 2016-06-21 12:35:56
● 2016-11-04 15:17:44
● 2026-05-13 02:27:00
○ 2026-06-18 23:57:12

●MXaspmx.l.google.com2008-03-20 → 2026-06-18 · 2 obs

● 2008-03-20 09:29:04
● 2026-06-18 23:57:12

●MXaspmx2.googlemail.com2008-03-20 → 2026-06-18 · 5 obs

● 2008-03-20 09:29:04
● 2016-04-04 00:23:48
○ 2016-06-21 12:35:56
○ 2026-05-13 02:27:00
● 2026-06-18 23:57:12

●A195.250.26.662026-05-11 → 2026-06-18 · 3 obs

○ 2016-12-15 13:20:20
● 2026-05-11 06:41:56
● 2026-06-18 23:57:12

○A198.154.115.2342015-07-22 → 2016-09-10 · 5 obs

○ 2008-03-20 09:29:04
● 2015-07-22 15:07:46
● 2016-09-10 07:31:50
○ 2016-11-04 15:17:44
○ 2026-06-18 23:57:12

○A204.93.248.922016-11-04 → 2016-12-15 · 5 obs

○ 2016-09-10 07:31:50
● 2016-11-04 15:17:44
● 2016-12-15 13:20:20
○ 2026-05-11 06:41:56
○ 2026-06-18 23:57:12

○A75.126.202.882008-03-20 → 2008-03-20 · 3 obs

● 2008-03-20 09:29:04
○ 2015-07-22 15:07:46
○ 2026-06-18 23:57:12

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
indobyte.com	ns100.webhostingbuzz.com, ns101.webhostingbuzz.com	2 records

✅ Authoritative Response

Server:192.243.110.201

NS records: ns100.webhostingbuzz.com, ns101.webhostingbuzz.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for indobyte.com (unsigned zone)

⏱️ Timing

Total: 191ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`195.250.26.66`
NS	2	`ns101.webhostingbuzz.com, ns100.webhostingbuzz.com`
MX	3	`aspmx2.googlemail.com (pri: 10), aspmx.l.google.com (pri: 1)...`
TXT	1	`v=spf1 +a +mx +ip4:195.250.26.61 include`
SOA	1	`ns100.webhostingbuzz.com servers.mysecur`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns100.webhostingbuzz.com, ns101.webhostingbuzz.com)

Analysis

IP Addresses

indobyte.com directs to one IP number, which is 195.250.26.66.

Among the host names that share IP numbers with indobyte.com are dksoutdoors.com.au, (0x616e616c)ytica.es, ninjahost.com and two others.

Name Servers

DNS delegation for indobyte.com points to two name servers: ns100.webhostingbuzz.com and ns101.webhostingbuzz.com.

indobyte.com has the same name server delegation as a number of other domains, such as justinhartleyonline.com, markrnesbitt.com, zeenqueen.com and two more.

There is at least partial name server overlap between indobyte.com and other domains — dejalulu.com, halcyonplus.com, tubes.rs and two more among them.

These name servers regularly appear alongside ns100.whbdns.com, ns101.whbdns.com, ns100.nsresponse.com and 4 other name servers in NS record sets.

ns100.webhostingbuzz.com → 192.243.110.201 and ns101.webhostingbuzz.com → 192.250.239.210: one IP number per host name.

Mail Servers

Incoming mail for indobyte.com is delivered via three mail servers: aspmx2.googlemail.com, aspmx.l.google.com and alt1.aspmx.l.google.com.

indobyte.com shares at least some of its mail servers with other domains — for example nicelydonemagick.com, ns500698.ns500759.ns500759.ns500759.ns500758.ns500735.ns500736.ns500735.ns500698.ns500736.ns500735.ns500576.ns500708.ns500576.ns500619.ns500576.ns500576.trackreceptor.com, ns500758.ns500698.ns500758.ns500735.ns500736.ns500735.ns500735.ns500735.ns500735.ns500698.ns500576.ns500576.ns500686.ns500619.ns500619.trackreceptor.com and two more.

It is common to find these mail servers paired with mail servers alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, alt4.aspmx.l.google.com and 3 more.

aspmx2.googlemail.com points to 108.177.123.27 and 2800:3f0:4003:c0f::1b. aspmx.l.google.com points to 142.250.31.27 and 2607:f8b0:4004:c1f::1a. alt1.aspmx.l.google.com points to 108.177.123.26 and 2800:3f0:4003:c0f::1b. All three hostnames carry two IP addresses, and 2800:3f0:4003:c0f::1b is shared between aspmx2.googlemail.com and alt1.aspmx.l.google.com.

Host names pointing to 2800:3f0:4003:c0f::1b IP addresses: aspmx2.googlemail.com and alt1.aspmx.l.google.com.