tryges.be - dns.ninja
tryges.be
be
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.nsset.be ⭐ | ||||||
| NS | b.nsset.be | ||||||
| NS | c.nsset.be | ||||||
| NS | d.nsset.be | ||||||
| NS | y.nsset.be | ||||||
| NS | z.nsset.be | ||||||
| SOA | a.nsset.bebe-hostmaster@dnsbelgium.be serial=1028256161 | ||||||
Same first word
Similar names
DNS History
9 records (9 active, 0 former)
●NSns1.edpnet.net2026-06-28 → 2026-08-04 · 3 obs
● 2026-06-28 01:41:20
● 2026-08-04 10:19:36
●NSns2.edpnet.net2026-06-28 → 2026-08-04 · 3 obs
● 2026-06-28 01:41:20
● 2026-08-04 10:19:36
●MXalt1.aspmx.l.google.com2015-06-07 → 2026-08-04 · 2 obs
● 2026-08-04 10:19:36
●MXalt2.aspmx.l.google.com2015-06-07 → 2026-08-04 · 2 obs
● 2026-08-04 10:19:36
●MXaspmx.l.google.com2015-06-07 → 2026-08-04 · 2 obs
● 2026-08-04 10:19:36
●MXaspmx2.googlemail.com2015-06-07 → 2026-08-04 · 2 obs
● 2026-08-04 10:19:36
●MXaspmx3.googlemail.com2015-06-07 → 2026-08-04 · 2 obs
● 2026-08-04 10:19:36
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| be | a.nsset.be, b.nsset.be, c.nsset.be, d.nsset.be... | - |
| tryges.be | ns1.edpnet.be, ns1.edpnet.net, ns2.edpnet.be, ns2.edpnet.net | 2 records |
✅ Authoritative Response
Server:212.71.8.11
NS records: ns1.edpnet.be, ns1.edpnet.net, ns2.edpnet.be, ns2.edpnet.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for tryges.be (unsigned zone)
⏱️ Timing
Total: 684ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | ns1.edpnet.be, ns2.edpnet.be |
| MX | 5 | aspmx3.googlemail.com (pri: 30), aspmx.l.google.com (pri: 10)... |
| TXT | 2 | MS=ms42579268, google-site-verification=yZwbVMfvHsW5o_H |
| SOA | 1 | ns1.edpnet.be admin.edpnet.net |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.edpnet.be, ns2.edpnet.be)
Analysis
Name Servers
The domain tryges.be is delegated to these four name servers: ns1.edpnet.be, ns2.edpnet.be, ns1.edpnet.net and ns2.edpnet.net.
There is at least partial name server overlap between tryges.be and other domains — 181.211.213.in-addr.arpa, 245.132.79.in-addr.arpa, 182.219.213.in-addr.arpa and two more among them.
Each of ns1.edpnet.be, ns2.edpnet.be, ns1.edpnet.net and ns2.edpnet.net resolves to two IP numbers, falling into two groups: ns1.edpnet.be and ns1.edpnet.net share 212.71.0.2 and 2a02:578:8000:2:212:71:0:2, while ns2.edpnet.be and ns2.edpnet.net share 212.71.8.11 and 2a02:578:1001:3:212:71:8:11.
Both ns1.edpnet.be and ns1.edpnet.net resolve to 2a02:578:8000:2:212:71:0:2 IP addresses each.
Both ns1.edpnet.be and ns1.edpnet.net resolve to 212.71.0.2 IP addresses each.
Both ns2.edpnet.be and ns2.edpnet.net resolve to 2a02:578:1001:3:212:71:8:11 IP addresses each.
Both ns2.edpnet.be and ns2.edpnet.net resolve to 212.71.8.11 IP addresses each.
Mail Servers
tryges.be has five mail servers, which are aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
tryges.be shares at least some of its mail servers with other domains — for example swiatek.info, clarksvillede.com, pagsim.com and two more.
It is common to find these mail servers paired with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 more.
Hosts with two IP numbers each:
aspmx2.googlemail.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
aspmx3.googlemail.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com directs traffic to 142.251.16.27 and 2607:f8b0:4004:c1b::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::1a.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c0f::1a IP addresses each.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 108.177.123.26 IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 2a00:1450:400b:c02::1a IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.27 IP addresses each.