parser.by - dns.ninja
parser.by
| DNSSEC | ⚠️ Not signed | ||||||
| NS | u1.hoster.by ⭐ | ||||||
| A | 2a0a:7d80:1:1::4:0🇧🇾 BELPAK-AS2a0a:7d80:1::/48 | ||||||
| PTR | u1.hoster.by | ||||||
| A | 93.125.30.201🇧🇾 BELPAK-AS93.125.30.0/24 DELEGATED FROM BELPAK | ||||||
| PTR | u1.hoster.by | ||||||
| NS | u2.hoster.by | ||||||
| A | 2a0a:7d80:3:1::3🇧🇾 HOSTERBY-AS2a0a:7d80:3::/48 hoster.by Velcom-DC IPv6 route object | ||||||
| PTR | net-2a0a-7d80-3-1-prefix-64.hosterby.com | ||||||
| A | 185.179.82.101🇧🇾 BN-AS185.179.82.0/23 BN for HOSTERBY | ||||||
| PTR | u2.hoster.by | ||||||
| SOA | u1.hoster.bysupport@hoster.by 2025-07-10 #14 | ||||||
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.bysupport@becloud.by serial=2608020940 | ||||||
Same first word
Similar names
DNS History
10 records (2 active, 8 former)
○NSns1.extasy-cms.com2015-08-13 → 2019-05-01 · 4 obs
● 2015-08-13 18:19:40
● 2019-05-01 05:43:16
○ 2026-02-26 15:49:20
○ 2026-08-02 09:48:34
● 2019-05-01 05:43:16
○ 2026-02-26 15:49:20
○ 2026-08-02 09:48:34
○NSns2.extasy-cms.com2015-08-13 → 2019-05-01 · 4 obs
● 2015-08-13 18:19:40
● 2019-05-01 05:43:16
○ 2026-02-26 15:49:20
○ 2026-08-02 09:48:34
● 2019-05-01 05:43:16
○ 2026-02-26 15:49:20
○ 2026-08-02 09:48:34
●NSu1.hoster.by2026-02-26 → 2026-08-02 · 3 obs
○ 2019-05-01 05:43:16
● 2026-02-26 15:49:20
● 2026-08-02 09:48:34
● 2026-02-26 15:49:20
● 2026-08-02 09:48:34
●NSu2.hoster.by2026-02-26 → 2026-08-02 · 3 obs
○ 2019-05-01 05:43:16
● 2026-02-26 15:49:20
● 2026-08-02 09:48:34
● 2026-02-26 15:49:20
● 2026-08-02 09:48:34
○MXalt1.aspmx.l.google.com2015-08-13 → 2019-05-01 · 4 obs
● 2015-08-13 18:19:40
● 2019-05-01 05:43:16
○ 2026-02-26 15:49:20
○ 2026-08-02 09:48:34
● 2019-05-01 05:43:16
○ 2026-02-26 15:49:20
○ 2026-08-02 09:48:34
○MXalt2.aspmx.l.google.com2015-08-13 → 2019-05-01 · 4 obs
● 2015-08-13 18:19:40
● 2019-05-01 05:43:16
○ 2026-02-26 15:49:20
○ 2026-08-02 09:48:34
● 2019-05-01 05:43:16
○ 2026-02-26 15:49:20
○ 2026-08-02 09:48:34
○MXaspmx.l.google.com2015-08-13 → 2019-05-01 · 4 obs
● 2015-08-13 18:19:40
● 2019-05-01 05:43:16
○ 2026-02-26 15:49:20
○ 2026-08-02 09:48:34
● 2019-05-01 05:43:16
○ 2026-02-26 15:49:20
○ 2026-08-02 09:48:34
○MXaspmx2.googlemail.com2015-08-13 → 2019-05-01 · 4 obs
● 2015-08-13 18:19:40
● 2019-05-01 05:43:16
○ 2026-02-26 15:49:20
○ 2026-08-02 09:48:34
● 2019-05-01 05:43:16
○ 2026-02-26 15:49:20
○ 2026-08-02 09:48:34
○MXaspmx3.googlemail.com2015-08-13 → 2019-05-01 · 4 obs
● 2015-08-13 18:19:40
● 2019-05-01 05:43:16
○ 2026-02-26 15:49:20
○ 2026-08-02 09:48:34
● 2019-05-01 05:43:16
○ 2026-02-26 15:49:20
○ 2026-08-02 09:48:34
○A78.46.78.872015-08-13 → 2019-05-01 · 4 obs
● 2015-08-13 18:19:40
● 2019-05-01 05:43:16
○ 2026-02-26 15:49:20
○ 2026-08-02 09:48:34
● 2019-05-01 05:43:16
○ 2026-02-26 15:49:20
○ 2026-08-02 09:48:34
🔍 DNS Trace
Analysis
Name Servers
parser.by has two authoritative name servers — u1.hoster.by and u2.hoster.by.
parser.by shares its NS records with other domains, for example lik.by, bsmu.by, ees.su and two others.
The name servers for parser.by overlap at least partially with those of other domains — for example korsil.ru.
Both u1.hoster.by and u2.hoster.by have two IP addresses each. u1.hoster.by resolves to 93.125.30.201 and 2a0a:7d80:1:1::4:0; u2.hoster.by resolves to 185.179.82.101 and 2a0a:7d80:3:1::3.