optimization.by - dns.ninja

`optimization.by`

DNSSEC	⚠️ Not signed
A	178.172.172.48^{🇧🇾 BELPAK-AS178.172.172.0/23}
		PTR	`178-172-172-48.hosterby.com`
NS	`a1.domain.by` ⭐
		A	93.85.84.141^{🇧🇾 BELPAK-AS93.85.84.0/22}
NS	`a2.domain.by`
		A	2a02:2208:1:5::301^{🇧🇾 BELPAK-AS2a02:2208:1::/48}
		A	93.84.119.247^{🇧🇾 BELPAK-AS93.84.112.0/21}
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c23::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadrs-in-f26.1e100.net`
		A	192.178.155.26^{🇺🇸 Google192.178.155.0/24}
			PTR	`yuiadrs-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	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
SOA	`a1.domain.by`info@domain.by 2022-06-04 #1

`by`

	DNSSEC	🔒 Signed (DS record present)
	NS	`dns1.tld.becloud.by` ⭐
	NS	`dns1.tld.becloudby.com`
	NS	`dns2.tld.becloudby.tech`
	NS	`dns3.tld.becloudby.tech`
	NS	`dns4.tld.becloudby.tech`
	NS	`dns7.tld.becloudby.com`
	SOA	`dns1.tld.becloud.by`support@becloud.by serial=2606151400

WOT: SAFE (66/100)

Same first word

DNS History

17 records (8 active, 9 former)

●NSa1.domain.by2017-10-02 → 2026-06-15 · 3 obs

○ 2016-07-24 03:24:52
● 2017-10-02 22:58:12
● 2026-06-15 14:15:34

●NSa2.domain.by2017-10-02 → 2026-06-15 · 3 obs

○ 2016-07-24 03:24:52
● 2017-10-02 22:58:12
● 2026-06-15 14:15:34

○NSns1.activeby.net2015-05-13 → 2016-07-24 · 4 obs

● 2015-05-13 12:51:00
● 2016-07-24 03:24:52
○ 2017-10-02 22:58:12
○ 2026-06-15 14:15:34

○NSns2.activeby.net2015-05-13 → 2016-07-24 · 4 obs

● 2015-05-13 12:51:00
● 2016-07-24 03:24:52
○ 2017-10-02 22:58:12
○ 2026-06-15 14:15:34

○NSns3.activeby.net2015-05-13 → 2016-07-24 · 4 obs

● 2015-05-13 12:51:00
● 2016-07-24 03:24:52
○ 2017-10-02 22:58:12
○ 2026-06-15 14:15:34

●MXalt1.aspmx.l.google.com2015-05-13 → 2026-06-15 · 2 obs

● 2015-05-13 12:51:00
● 2026-06-15 14:15:34

●MXalt2.aspmx.l.google.com2015-05-13 → 2026-06-15 · 2 obs

● 2015-05-13 12:51:00
● 2026-06-15 14:15:34

●MXalt3.aspmx.l.google.com2017-10-02 → 2026-06-15 · 3 obs

○ 2016-07-24 03:24:52
● 2017-10-02 22:58:12
● 2026-06-15 14:15:34

●MXalt4.aspmx.l.google.com2017-10-02 → 2026-06-15 · 3 obs

○ 2016-07-24 03:24:52
● 2017-10-02 22:58:12
● 2026-06-15 14:15:34

●MXaspmx.l.google.com2015-05-13 → 2026-06-15 · 2 obs

● 2015-05-13 12:51:00
● 2026-06-15 14:15:34

○MXaspmx2.googlemail.com2015-05-13 → 2016-07-24 · 4 obs

● 2015-05-13 12:51:00
● 2016-07-24 03:24:52
○ 2017-10-02 22:58:12
○ 2026-06-15 14:15:34

○MXaspmx3.googlemail.com2015-05-13 → 2016-07-24 · 4 obs

● 2015-05-13 12:51:00
● 2016-07-24 03:24:52
○ 2017-10-02 22:58:12
○ 2026-06-15 14:15:34

○MXaspmx4.googlemail.com2015-05-13 → 2016-07-24 · 4 obs

● 2015-05-13 12:51:00
● 2016-07-24 03:24:52
○ 2017-10-02 22:58:12
○ 2026-06-15 14:15:34

○MXaspmx5.googlemail.com2015-05-13 → 2016-07-24 · 4 obs

● 2015-05-13 12:51:00
● 2016-07-24 03:24:52
○ 2017-10-02 22:58:12
○ 2026-06-15 14:15:34

○A178.124.135.772015-05-13 → 2016-07-24 · 4 obs

● 2015-05-13 12:51:00
● 2016-07-24 03:24:52
○ 2017-10-02 22:58:12
○ 2026-06-15 14:15:34

○A178.172.172.1262017-10-02 → 2017-10-02 · 4 obs

○ 2016-07-24 03:24:52
● 2017-10-02 22:58:12
○ 2026-03-08 20:38:28
○ 2026-06-15 14:15:34

●A178.172.172.482026-03-08 → 2026-06-15 · 3 obs

○ 2017-10-02 22:58:12
● 2026-03-08 20:38:28
● 2026-06-15 14:15:34

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
by	dns1.tld.becloudby.com, dns2.tld.becloudby.tech, dns3.tld.becloudby.tech, dns4.tld.becloudby.tech...	-
optimization.by	a1.domain.by, a2.domain.by	-

✅ Authoritative Response

Server:93.85.84.141

NS records: a1.domain.by, a2.domain.by

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for optimization.by (unsigned zone)

⏱️ Timing

Total: 1262ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`178.172.172.48`
NS	2	`a2.domain.by, a1.domain.by`
MX	5	`alt3.aspmx.l.google.com (pri: 10), alt4.aspmx.l.google.com (pri: 10)...`
SOA	1	`a1.domain.by info.domain.by`

Analysis

IP Addresses

optimization.by points to a single IP number: 178.172.172.48.

Additional host names — port-134-adslby-pool-91-187-1.infonet.by, port-228-adslby-pool40.infonet.by, port-50-adslby-pool42.infonet.by and two others — share IP numbers with optimization.by.

Name Servers

optimization.by uses two name servers for its delegation: a1.domain.by and a2.domain.by.

optimization.by shares its name server setup with other domains, including andrey.by, alfacrm.by, emperador.by and two others.

Host names with two IP numbers:

a2.domain.by directs traffic to 93.84.119.247 and 2a02:2208:1:5::301.

Host names pointing to a single IP address:

a1.domain.by has the IP address 93.85.84.141.

Mail Servers

optimization.by is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

optimization.by shares mail servers — at least in part — with other domains, including ns500821.ns500841.ns500794.ns500841.ns500841.ns500794.ns500821.ns500795.ns500794.ns500794.ns500821.ns500790.lustypartnersfinder.com, mediumvergelijker.nl, ns500765.ns500693.ns500693.ns500699.ns500693.ns500734.ns500728.ns500728.ns500683.ns500588.ns500588.ns500588.ns500588.ns500588.ns500588.dtrkdll.com and two others.

These mail servers are frequently used alongside mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 other.

Host names with two IP numbers:

aspmx.l.google.com directs traffic to 192.178.155.26 and 2607:f8b0:4004:c23::1a.

alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.

alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.

alt3.aspmx.l.google.com directs traffic to 192.178.223.26 and 2a00:1450:4009:c0f::1b.

alt4.aspmx.l.google.com directs traffic to 172.253.157.26 and 2a00:1450:400c:c23::1a.