wedding.by - robtex.com
wedding.by
| DNSSEC | ⚠️ Not signed | ||||||
| A | 194.62.19.12🇧🇾 SUPPORTCHAIN-AS194.62.19.0/24 | ||||||
| PTR | 12.19.62.194.static.hostfyby.net | ||||||
| NS | wedding.by ⭐ | ||||||
| A | 194.62.19.12🇧🇾 SUPPORTCHAIN-AS194.62.19.0/24 | ||||||
| PTR | 12.19.62.194.static.hostfyby.net | ||||||
| NS | park1.hostfly.by | ||||||
| A | 85.209.148.117🇧🇾 SUPPORTCHAIN-AS85.209.148.0/24 | ||||||
| PTR | 117.148.209.85.static.hostfyby.net | ||||||
| NS | park2.hostfly.by | ||||||
| A | 85.209.148.122🇧🇾 SUPPORTCHAIN-AS85.209.148.0/24 | ||||||
| PTR | 122.148.209.85.static.hostfyby.net | ||||||
| SOA | wedding.bypark1@hostfly.by 2022-07-19 #0 | ||||||
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=2604131250 | ||||||
NS for
wedding.by |
Same first word
Similar names
DNS History
7 records (4 active, 3 former)
●NSpark1.hostfly.by2026-04-02 → 2026-04-13 · 3 obs
● 2026-04-02 12:00:18
● 2026-04-13 13:16:12
●NSpark2.hostfly.by2026-04-02 → 2026-04-13 · 3 obs
● 2026-04-02 12:00:18
● 2026-04-13 13:16:12
○NSu1.hoster.by2015-07-08 → 2016-07-18 · 4 obs
● 2016-07-18 18:59:12
○ 2026-04-02 12:00:18
○ 2026-04-13 13:16:12
○NSu2.hoster.by2015-07-08 → 2016-07-18 · 4 obs
● 2016-07-18 18:59:12
○ 2026-04-02 12:00:18
○ 2026-04-13 13:16:12
●NSwedding.by2026-04-02 → 2026-04-13 · 3 obs
● 2026-04-02 12:00:18
● 2026-04-13 13:16:12
●A194.62.19.122026-04-02 → 2026-04-13 · 3 obs
● 2026-04-02 12:00:18
● 2026-04-13 13:16:12
○A93.84.112.902015-07-08 → 2016-07-18 · 4 obs
● 2016-07-18 18:59:12
○ 2026-04-02 12:00:18
○ 2026-04-13 13:16:12
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| by | dns1.tld.becloudby.com, dns7.tld.becloudby.com, dns2.tld.becloudby.tech, dns3.tld.becloudby.tech... | 9 records |
| wedding.by | park1.hostfly.by, park2.hostfly.by | - |
✅ Authoritative Response
Server:85.209.148.117
NS records: park1.hostfly.by, park2.hostfly.by
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for wedding.by (unsigned zone)
⏱️ Timing
Total: 1393ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 194.62.19.12 |
| NS | 2 | park1.hostfly.by, park2.hostfly.by |
| SOA | 1 | wedding.by park1.hostfly.by |
📌 Glue Records Collected
Total: 9
Out-of-bailiwick: 9 (dns1.tld.becloudby.com, dns1.tld.becloudby.com, dns7.tld.becloudby.com...)
Analysis
Name Server Role
wedding.by serves as a name server for wedding.by.
park1.hostfly.by and park2.hostfly.by are commonly used as name servers together with wedding.by.
IP Addresses
wedding.by points to an IP address: 194.62.19.12.
other host names include perevod.by, aromat.by, borisov.by, pb.by and bb.by; they share IP numbers with wedding.by.
Name Servers
wedding.by is delegated to three name servers: wedding.by, park1.hostfly.by and park2.hostfly.by.
wedding.by at least partially shares name servers with other domains, for instance lumen.by, simply.by, magia.by, belpay.by and tur.by.
These name servers are commonly used alongside domainnames.by.
Host names with one IP:
wedding.by points to 194.62.19.12; park1.hostfly.by points to 85.209.148.117; park2.hostfly.by points to 85.209.148.122.