parser.by - dns.ninja

parser.by

DNSSEC⚠️ Not signed
NSu1.hoster.by
A2a0a:7d80:1:1::4:0🇧🇾 BELPAK-AS2a0a:7d80:1::/48
PTRu1.hoster.by
A93.125.30.201🇧🇾 BELPAK-AS93.125.30.0/24 DELEGATED FROM BELPAK
PTRu1.hoster.by
NSu2.hoster.by
A2a0a:7d80:3:1::3🇧🇾 HOSTERBY-AS2a0a:7d80:3::/48 hoster.by Velcom-DC IPv6 route object
PTRnet-2a0a-7d80-3-1-prefix-64.hosterby.com
A185.179.82.101🇧🇾 BN-AS185.179.82.0/23 BN for HOSTERBY
PTRu2.hoster.by
SOAu1.hoster.bysupport@hoster.by 2025-07-10 #14

by

DNSSEC🔒 Signed (DS record present)
NSdns1.tld.becloud.by
NSdns1.tld.becloudby.com
NSdns2.tld.becloudby.tech
NSdns3.tld.becloudby.tech
NSdns4.tld.becloudby.tech
NSdns7.tld.becloudby.com
SOAdns1.tld.becloud.bysupport@becloud.by serial=2608021900
WOT: SAFE (25/100)

Same first word

Similar names

DNS History

10 records (2 active, 8 former)

20162017201820192020202120222023202420252026NSu1.hoster.byu2.hoster.byns1.extasy-cms.comns2.extasy-cms.comMXalt1.aspmx.l.google.comalt2.aspmx.l.google.comaspmx.l.google.comaspmx2.googlemail.comaspmx3.googlemail.comA78.46.78.87
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 19:09:08
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 19:09:08
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 19:09:08
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 19:09:08
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 19:09:08
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 19:09:08
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 19:09:08
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 19:09:08
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 19:09:08
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 19:09:08

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
bydns2.tld.becloudby.tech, dns4.tld.becloudby.tech, dns7.tld.becloudby.com, dns1.tld.becloudby.com...9 records
parser.byu1.hoster.by, u2.hoster.by-

✅ Authoritative Response

Server:185.179.82.101

NS records: u1.hoster.by, u2.hoster.by

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for parser.by (unsigned zone)

⏱️ Timing

Total: 690ms | Queries: -

📄 Records

TypeCountSample Data
NS2u1.hoster.by, u2.hoster.by
SOA1u1.hoster.by support.hoster.by

📌 Glue Records Collected

Total: 9

Out-of-bailiwick: 9 (dns7.tld.becloudby.com, dns4.tld.becloudby.tech, dns3.tld.becloudby.tech...)

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.