resify.com - dns.ninja
resify.com
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1784338337 | ||||||
Same first word
resify.com |
Similar names
DNS History
13 records (10 active, 3 former)
●NSns1.name.com2015-08-07 → 2026-07-18 · 5 obs
● 2017-02-06 23:45:26
○ 2018-10-20 18:55:44
● 2026-04-23 05:44:22
● 2026-07-18 01:35:44
●NSns1djs.name.com2018-10-20 → 2026-07-18 · 3 obs
● 2018-10-20 18:55:44
● 2026-07-18 01:35:44
○NSns2.name.com2015-08-07 → 2017-02-06 · 4 obs
● 2017-02-06 23:45:26
○ 2018-10-20 18:55:44
○ 2026-07-18 01:35:44
●NSns2dky.name.com2018-10-20 → 2026-07-18 · 3 obs
● 2018-10-20 18:55:44
● 2026-07-18 01:35:44
○NSns3.name.com2015-08-07 → 2017-02-06 · 4 obs
● 2017-02-06 23:45:26
○ 2018-10-20 18:55:44
○ 2026-07-18 01:35:44
●NSns3gmt.name.com2018-10-20 → 2026-07-18 · 3 obs
● 2018-10-20 18:55:44
● 2026-07-18 01:35:44
○NSns4.name.com2015-08-07 → 2017-02-06 · 4 obs
● 2017-02-06 23:45:26
○ 2018-10-20 18:55:44
○ 2026-07-18 01:35:44
●NSns4dfh.name.com2018-10-20 → 2026-07-18 · 3 obs
● 2018-10-20 18:55:44
● 2026-07-18 01:35:44
●MXalt1.aspmx.l.google.com2015-08-07 → 2026-07-18 · 2 obs
● 2026-07-18 01:35:44
●MXalt2.aspmx.l.google.com2015-08-07 → 2026-07-18 · 2 obs
● 2026-07-18 01:35:44
●MXaspmx.l.google.com2015-08-07 → 2026-07-18 · 2 obs
● 2026-07-18 01:35:44
●MXaspmx2.googlemail.com2015-08-07 → 2026-07-18 · 2 obs
● 2026-07-18 01:35:44
●MXaspmx3.googlemail.com2015-08-07 → 2026-07-18 · 2 obs
● 2026-07-18 01:35:44
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | m.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, f.gtld-servers.net... | - |
| resify.com | ns1djs.name.com, ns2dky.name.com, ns3gmt.name.com, ns4dfh.name.com | 8 records |
✅ Authoritative Response
Server:163.114.216.17
NS records: ns1djs.name.com, ns2dky.name.com, ns3gmt.name.com, ns4dfh.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for resify.com (unsigned zone)
⏱️ Timing
Total: 1874ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns1djs.name.com, ns2dky.name.com... |
| MX | 5 | alt1.aspmx.l.google.com (pri: 20), alt2.aspmx.l.google.com (pri: 30)... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns1djs.name.com, ns1djs.name.com, ns2dky.name.com...)
Analysis
Name Servers
resify.com has five name servers, which are ns1.name.com, ns1djs.name.com, ns2dky.name.com and two others.
There is at least partial name server overlap between resify.com and other domains — xplayer.life, devsecops.world, loganspencer.com and two more among them.
These name servers regularly appear alongside ns4dfh.name.com, ns3gmt.name.com, ns1cnb.name.com and 7 other name servers in NS record sets.
Hostnames that resolve to two IP addresses:
ns1.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns1djs.name.com directs traffic to 163.114.216.17 and 2a00:edc0:107::1.
ns2dky.name.com directs traffic to 163.114.216.49 and 2402:cf80:107::1.
ns3gmt.name.com directs traffic to 163.114.217.17 and 2a00:edc0:107::49.
ns4dfh.name.com directs traffic to 163.114.217.49 and 2402:cf80:107::49.
Both ns1.name.com and ns1djs.name.com resolve to 2a00:edc0:107::1 IP addresses each.
Both ns1.name.com and ns1djs.name.com resolve to 163.114.216.17 IP addresses each.
Mail Servers
Five mail servers handle resify.com: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
resify.com has at least partial mail server overlap with other domains such as ns500699.ns500699.ns500693.ns500734.ns500699.ns500699.ns500699.ns500693.ns500699.ns500699.ns500588.ns500588.ns500588.ns500693.ns500588.ns500110.dtrkdll.com, ns500765.ns500699.ns500699.ns500693.ns500699.ns500693.ns500734.ns500734.ns500699.ns500693.ns500588.ns500588.ns500588.ns500632.ns500588.ns500588.ns500588.dtrkdll.com, ns500742.ns500754.ns500742.ns500671.ns500671.ns500742.ns500704.ns500731.ns500704.ns500742.ns500705.ns500704.ns500671.ns500649.ns500649.lustychickser.com and two more.
These mail servers commonly co-occur with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.
Hostnames that resolve to two IP addresses:
aspmx2.googlemail.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1b.
aspmx3.googlemail.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com directs traffic to 64.233.180.26 and 2607:f8b0:4004:c1b::1a.
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 aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 172.253.116.26 IP addresses each.