technicallyresolution.com - dns.ninja
technicallyresolution.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=1786239164 | ||||||
Same first word
technicallyresolution.com |
DNS History
16 records (16 active, 0 former)
●NSns1.publicdnsservice.com2026-04-11 → 2026-08-09 · 2 obs
● 2026-08-09 01:54:38
●NSns2.publicdnsservice.com2026-04-11 → 2026-08-09 · 2 obs
● 2026-08-09 01:54:38
●A172.240.108.682026-04-11 → 2026-08-09 · 2 obs
● 2026-08-09 01:54:38
●A172.240.108.762026-04-11 → 2026-08-09 · 2 obs
● 2026-08-09 01:54:38
●A172.240.108.842026-04-11 → 2026-08-09 · 2 obs
● 2026-08-09 01:54:38
●A172.240.127.2342026-04-11 → 2026-08-09 · 2 obs
● 2026-08-09 01:54:38
●A172.240.127.2422026-04-11 → 2026-08-09 · 2 obs
● 2026-08-09 01:54:38
●A172.240.127.2432026-04-11 → 2026-08-09 · 2 obs
● 2026-08-09 01:54:38
●A172.240.127.2442026-04-11 → 2026-08-09 · 2 obs
● 2026-08-09 01:54:38
●A172.240.253.1322026-04-11 → 2026-08-09 · 2 obs
● 2026-08-09 01:54:38
●A172.255.141.42026-08-09 → 2026-08-09 · 2 obs
● 2026-08-09 01:54:38
●A23.111.84.1162026-08-09 → 2026-08-09 · 2 obs
● 2026-08-09 01:54:38
●A23.111.84.1242026-08-09 → 2026-08-09 · 2 obs
● 2026-08-09 01:54:38
●A23.111.84.2202026-08-09 → 2026-08-09 · 2 obs
● 2026-08-09 01:54:38
●A23.111.84.2282026-08-09 → 2026-08-09 · 2 obs
● 2026-08-09 01:54:38
●A23.111.84.42026-08-09 → 2026-08-09 · 2 obs
● 2026-08-09 01:54:38
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | b.gtld-servers.net, h.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net... | - |
| technicallyresolution.com | ns1.publicdnsservice.com, ns2.publicdnsservice.com | 2 records |
✅ Authoritative Response
Server:52.223.51.231
NS records: ns1.publicdnsservice.com, ns2.publicdnsservice.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for technicallyresolution.com (unsigned zone)
⏱️ Timing
Total: 365ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 14 | 172.240.108.76, 172.240.127.234... |
| NS | 2 | ns1.publicdnsservice.com, ns2.publicdnsservice.com |
| SOA | 1 | ns1.publicdnsservice.com hostmaster.tech |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.publicdnsservice.com, ns2.publicdnsservice.com)
Analysis
IP Addresses
technicallyresolution.com points to 14 IP addresses, including 23.111.84.4, 23.111.84.116 and 23.111.84.124, plus 11 other.
concerntyreaimless.com, literallyflickercomplaints.com, exceedinglytemperaturedeclared.com plus two other host names have IP numbers in common with technicallyresolution.com.
Name Servers
technicallyresolution.com is delegated to two name servers: ns1.publicdnsservice.com and ns2.publicdnsservice.com.
The name server configuration of technicallyresolution.com is shared with other domains, for instance distractingzodiacperpetrate.com, anticipationcandiddeserted.com, factorynobody.com and two others.
technicallyresolution.com shares at least some of its name servers with other domains, such as capricerecording.com.
ns1.publicdnsservice.com and ns2.publicdnsservice.com each resolve to one IP number: ns1.publicdnsservice.com points to 52.223.51.231 and ns2.publicdnsservice.com points to 99.83.185.193.