detectify.io - dns.ninja
detectify.io
io
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a0.nic.io ⭐ | ||||||
| NS | a2.nic.io | ||||||
| NS | b0.nic.io | ||||||
| NS | c0.nic.io | ||||||
| SOA | a0.nic.iohostmaster@donuts.email serial=1785947860 | ||||||
Same first word
detectify.se |
detectify.net |
detectify.org |
detectify.io |
detectify.nu |
detectify.de |
detectify.com |
detectify.party |
DNS History
7 records (7 active, 0 former)
●NSns-1049.awsdns-03.org2018-01-13 → 2026-08-05 · 2 obs
● 2026-08-05 17:13:02
●NSns-1981.awsdns-55.co.uk2018-01-13 → 2026-08-05 · 2 obs
● 2026-08-05 17:13:02
●NSns-203.awsdns-25.com2018-01-13 → 2026-08-05 · 2 obs
● 2026-08-05 17:13:02
●NSns-855.awsdns-42.net2018-01-13 → 2026-08-05 · 2 obs
● 2026-08-05 17:13:02
●MXalt1.aspmx.l.google.com2018-01-13 → 2026-08-05 · 2 obs
● 2026-08-05 17:13:02
●MXalt2.aspmx.l.google.com2018-01-13 → 2026-08-05 · 2 obs
● 2026-08-05 17:13:02
●MXaspmx.l.google.com2018-01-13 → 2026-08-05 · 2 obs
● 2026-08-05 17:13:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| io | a0.nic.io, a2.nic.io, b0.nic.io, c0.nic.io | - |
| detectify.io | ns-1981.awsdns-55.co.uk, ns-203.awsdns-25.com, ns-855.awsdns-42.net, ns-1049.awsdns-03.org | - |
✅ Authoritative Response
Server:205.251.196.25
NS records: ns-1981.awsdns-55.co.uk, ns-203.awsdns-25.com, ns-855.awsdns-42.net, ns-1049.awsdns-03.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for detectify.io (unsigned zone)
⏱️ Timing
Total: 535ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns-1049.awsdns-03.org, ns-1981.awsdns-55.co.uk... |
| MX | 3 | aspmx.l.google.com (pri: 10), alt1.aspmx.l.google.com (pri: 20)... |
| TXT | 1 | v=spf1 include:servers.mcsv.net include: |
| SOA | 1 | ns-855.awsdns-42.net awsdns-hostmaster.a |
Analysis
Name Servers
The NS records for detectify.io point to four name servers: ns-203.awsdns-25.com, ns-855.awsdns-42.net, ns-1049.awsdns-03.org and ns-1981.awsdns-55.co.uk.
detectify.io has at least partial name server overlap with other domains, such as ontraport.net, it-espresso.de, sandbox.ideonapi.com and two others.
ns-203.awsdns-25.com, ns-855.awsdns-42.net, ns-1049.awsdns-03.org and ns-1981.awsdns-55.co.uk all point to exactly two IP numbers each: ns-203.awsdns-25.com → 205.251.192.203 and 2600:9000:5300:cb00::1; ns-855.awsdns-42.net → 205.251.195.87 and 2600:9000:5303:5700::1; ns-1049.awsdns-03.org → 205.251.196.25 and 2600:9000:5304:1900::1; ns-1981.awsdns-55.co.uk → 205.251.199.189 and 2600:9000:5307:bd00::1.
Mail Servers
detectify.io has three mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com and alt2.aspmx.l.google.com.
There is at least a partial MX overlap between detectify.io and other domains, including egr.com.tr, ns500693.ns500765.ns500734.ns500699.ns500699.ns500699.ns500693.ns500693.ns500699.ns500683.ns500699.ns500588.ns500588.ns500632.ns500632.ns500110.dtrkdll.com, ns500724.ns500724.ns500724.ns500737.ns500724.ns500697.ns500583.ns500599.ns500583.ns500682.ns500599.yummyflingsfinder.com and two others.
These mail servers tend to appear in combination with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.
aspmx.l.google.com resolves to 172.253.115.26 and 2607:f8b0:4004:c08::1b. alt1.aspmx.l.google.com resolves to 108.177.123.27 and 2800:3f0:4003:c0f::1b. alt2.aspmx.l.google.com resolves to 172.253.116.26 and 2a00:1450:400b:c02::1a. All three hostnames point to two IP numbers each.