`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:c23::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadrs-in-f27.1e100.net`
		A	64.233.180.26^{🇺🇸 Google64.233.180.0/24}
			PTR	`on-in-f26.1e100.net`
			PTR	`pe-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 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=1783232436

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-07-05 06:22:30

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

○ 2016-12-15 13:20:20
● 2026-05-11 06:41:56
● 2026-07-05 06:22:30

○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-07-05 06:22:30

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

○ 2016-12-15 13:20:20
● 2026-05-11 06:41:56
● 2026-07-05 06:22:30

○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-07-05 06:22:30

○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-07-05 06:22:30

○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-07-05 06:22:30

○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-07-05 06:22:30

●MXalt1.aspmx.l.google.com2008-03-20 → 2026-07-05 · 2 obs

● 2008-03-20 09:29:04
● 2026-07-05 06:22:30

○MXalt2.aspmx.l.google.com2016-06-21 → 2026-05-13 · 5 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
○ 2026-07-05 06:22:30

○MXalt3.aspmx.l.google.com2016-11-04 → 2026-05-13 · 5 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
○ 2026-07-05 06:22:30

○MXalt4.aspmx.l.google.com2016-11-04 → 2026-05-13 · 5 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
○ 2026-07-05 06:22:30

●MXaspmx.l.google.com2008-03-20 → 2026-07-05 · 2 obs

● 2008-03-20 09:29:04
● 2026-07-05 06:22:30

●MXaspmx2.googlemail.com2008-03-20 → 2026-07-05 · 6 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
● 2026-07-05 06:22:30

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

○ 2016-12-15 13:20:20
● 2026-05-11 06:41:56
● 2026-07-05 06:22:30

○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-07-05 06:22:30

○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-07-05 06:22:30

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

● 2008-03-20 09:29:04
○ 2015-07-22 15:07:46
○ 2026-07-05 06:22:30

🔍 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: 229ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`195.250.26.66`
NS	2	`ns101.webhostingbuzz.com, ns100.webhostingbuzz.com`
MX	3	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
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 resolves to just one IP address, 195.250.26.66.

Two other host names, along with dksoutdoors.com.au, (0x616e616c)ytica.es and ninjahost.com, also share IP numbers with indobyte.com.

Name Servers

indobyte.com is delegated to two name servers: ns100.webhostingbuzz.com and ns101.webhostingbuzz.com.

indobyte.com shares its NS records with other domains, for example justinhartleyonline.com, markrnesbitt.com, zeenqueen.com and two others.

The name servers of indobyte.com overlap at least partially with those of other domains — among them dejalulu.com, halcyonplus.com, tubes.rs and two more.

These name servers commonly appear in delegations together with ns100.whbdns.com, ns101.whbdns.com, ns100.nsresponse.com and 3 other.

Both ns100.webhostingbuzz.com and ns101.webhostingbuzz.com have a single IP address each — ns100.webhostingbuzz.com resolves to 192.243.110.201 while ns101.webhostingbuzz.com resolves to 192.250.239.210.

Mail Servers

Mail for indobyte.com is routed through three mail servers — aspmx2.googlemail.com, aspmx.l.google.com and alt1.aspmx.l.google.com.

There is at least a partial MX overlap between indobyte.com and other domains, including 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 others.

These mail servers tend to appear in combination with mail servers alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, alt4.aspmx.l.google.com and 3 others.

aspmx2.googlemail.com, aspmx.l.google.com and alt1.aspmx.l.google.com each resolve to two IP addresses: aspmx2.googlemail.com resolves to 108.177.123.27 and 2800:3f0:4003:c0f::1b; aspmx.l.google.com resolves to 64.233.180.26 and 2607:f8b0:4004:c23::1b; alt1.aspmx.l.google.com resolves to 108.177.123.26 and 2800:3f0:4003:c0f::1a.

indobyte.com - robtex.com

indobyte.com

com

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

`indobyte.com`

`com`