angrybytes.eu - dns.ninja
angrybytes.eu
eu
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | si.dns.eu ⭐ | ||||||
| NS | be.dns.eu | ||||||
| NS | w.dns.eu | ||||||
| NS | x.dns.eu | ||||||
| NS | y.dns.eu | ||||||
| SOA | si.dns.eutech@eurid.eu serial=1125965169 | ||||||
Previously MX for
angrybytes.eu |
Same first word
Similar names
DNS History
17 records (12 active, 5 former)
●NSns0.transip.net2015-07-16 → 2026-07-10 · 2 obs
● 2026-07-10 09:21:38
○NSns1.transip.net2015-07-16 → 2017-04-10 · 4 obs
● 2017-04-10 12:52:00
○ 2026-04-07 18:46:46
○ 2026-07-10 09:21:38
●NSns1.transip.nl2026-04-07 → 2026-07-10 · 3 obs
● 2026-04-07 18:46:46
● 2026-07-10 09:21:38
●NSns2.transip.eu2026-04-07 → 2026-07-10 · 3 obs
● 2026-04-07 18:46:46
● 2026-07-10 09:21:38
○NSns2.transip.net2015-07-16 → 2017-04-10 · 4 obs
● 2017-04-10 12:52:00
○ 2026-04-07 18:46:46
○ 2026-07-10 09:21:38
●MXalt1.aspmx.l.google.com2015-07-16 → 2026-07-10 · 2 obs
● 2026-07-10 09:21:38
●MXalt2.aspmx.l.google.com2015-07-16 → 2026-07-10 · 2 obs
● 2026-07-10 09:21:38
○MXangrybytes.eu2015-07-16 → 2017-04-10 · 4 obs
● 2017-04-10 12:52:00
○ 2026-04-07 18:46:46
○ 2026-07-10 09:21:38
●MXaspmx.l.google.com2015-07-16 → 2026-07-10 · 2 obs
● 2026-07-10 09:21:38
●MXaspmx2.googlemail.com2015-07-16 → 2026-07-10 · 2 obs
● 2026-07-10 09:21:38
●MXaspmx3.googlemail.com2015-07-16 → 2026-07-10 · 2 obs
● 2026-07-10 09:21:38
●MXaspmx4.googlemail.com2015-07-16 → 2026-07-10 · 2 obs
● 2026-07-10 09:21:38
●MXaspmx5.googlemail.com2015-07-16 → 2026-07-10 · 2 obs
● 2026-07-10 09:21:38
●A168.119.212.322026-04-07 → 2026-07-10 · 3 obs
● 2026-04-07 18:46:46
● 2026-07-10 09:21:38
○A213.171.133.1042017-04-10 → 2017-04-10 · 4 obs
● 2017-04-10 12:52:00
○ 2026-04-07 18:46:46
○ 2026-07-10 09:21:38
●A2a01:4f8:251:1c1b::12026-04-07 → 2026-07-10 · 3 obs
● 2026-04-07 18:46:46
● 2026-07-10 09:21:38
○A83.96.195.1652015-07-16 → 2016-07-01 · 4 obs
● 2016-07-01 17:37:44
○ 2017-04-10 12:52:00
○ 2026-07-10 09:21:38
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| eu | be.dns.eu, x.dns.eu, y.dns.eu, w.dns.eu... | - |
| angrybytes.eu | ns0.transip.net, ns2.transip.eu, ns1.transip.nl | 2 records |
✅ Authoritative Response
Server:195.135.195.195
NS records: ns0.transip.net, ns2.transip.eu, ns1.transip.nl
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 1125ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 168.119.212.32 |
| AAAA | 1 | 2a01:4f8:251:1c1b::1 |
| NS | 3 | ns0.transip.net, ns1.transip.nl... |
| MX | 7 | ASPMX.L.google.com (pri: 10), ALT2.ASPMX.L.google.com (pri: 20)... |
| SOA | 1 | ns0.transip.net hostmaster.transip.nl |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns2.transip.eu, ns2.transip.eu)
Analysis
IP Addresses
angrybytes.eu resolves to the IP addresses 168.119.212.32 and 2a01:4f8:251:1c1b::1
angrybytes.nl, angrylog.com, tsn-794bdyfknw-productie.angrypix.com and two other host names share IP numbers with angrybytes.eu.
Name Servers
The authoritative name servers for angrybytes.eu are ns2.transip.eu, ns0.transip.net and ns1.transip.nl — three in total.
angrybytes.eu has at least partial name server overlap with other domains, such as tepmail.nl, imcd.be, beukhoreca.net and two others.
ns2.transip.eu, ns0.transip.net and ns1.transip.nl all resolve to exactly two IP numbers apiece: ns2.transip.eu → 37.97.199.195 and 2a01:7c8:f:c1f::195; ns0.transip.net → 195.135.195.195 and 2a01:7c8:dddd:195::195; ns1.transip.nl → 195.8.195.195 and 2a01:7c8:7000:195::195.
Mail Servers
Mail for angrybytes.eu is routed through 7 mail servers, including aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com and 4 other.
angrybytes.eu has at least partial mail server overlap with other domains such as grupocdr.com.mx, greatway.com.sg, magnetik.net.ua and two more.
These mail servers commonly co-occur with mail servers aspmx.l.google.com, alt2.aspmx.l.google.com, alt1.aspmx.l.google.com and 3 others.
Hostnames that resolve to two IP addresses:
aspmx2.googlemail.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
aspmx3.googlemail.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.
aspmx4.googlemail.com directs traffic to 192.178.223.26 and 2a00:1450:4009:c0f::1b.
aspmx5.googlemail.com directs traffic to 172.253.157.27 and 2a00:1450:400c:c23::1b.
aspmx.l.google.com directs traffic to 64.233.180.27 and 2607:f8b0:4004:c08::1b.
alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c0f::1b IP addresses each.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 108.177.123.27 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.26 IP addresses each.