technicallygeli.com - robtex.com
technicallygeli.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns31.domaincontrol.com ⭐ | ||||||
| A | 2603:5:2191::10🇺🇸 GODADDY-DNS2603:5:2190::/44 | ||||||
| PTR | ns31.domaincontrol.com | ||||||
| A | 97.74.105.16🇺🇸 GODADDY-DNS97.74.104.0/23 | ||||||
| PTR | ns31.domaincontrol.com | ||||||
| NS | ns32.domaincontrol.com | ||||||
| A | 2603:5:2291::10🇺🇸 GODADDY-DNS2603:5:2290::/44 | ||||||
| PTR | ns32.domaincontrol.com | ||||||
| A | 173.201.73.16🇺🇸 GODADDY-DNS173.201.72.0/23 | ||||||
| PTR | ns32.domaincontrol.com | ||||||
| SOA | ns31.domaincontrol.comdns@jomax.net 2025-11-21 #6 | ||||||
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=1771291435 | ||||||
Same first word
technicallygeli.com |
DNS History
15 records (2 active, 13 former)
○NSns-cloud-e1.googledomains.com2015-11-14 → 2017-02-07 · 5 obs
○ 2015-06-05 12:47:50
● 2015-11-14 03:32:24
● 2017-02-07 09:29:38
○ 2026-02-28 13:31:22
○ 2026-03-23 17:35:48
● 2015-11-14 03:32:24
● 2017-02-07 09:29:38
○ 2026-02-28 13:31:22
○ 2026-03-23 17:35:48
○NSns-cloud-e2.googledomains.com2015-11-14 → 2017-02-07 · 5 obs
○ 2015-06-05 12:47:50
● 2015-11-14 03:32:24
● 2017-02-07 09:29:38
○ 2026-02-28 13:31:22
○ 2026-03-23 17:35:48
● 2015-11-14 03:32:24
● 2017-02-07 09:29:38
○ 2026-02-28 13:31:22
○ 2026-03-23 17:35:48
○NSns-cloud-e3.googledomains.com2015-11-14 → 2017-02-07 · 5 obs
○ 2015-06-05 12:47:50
● 2015-11-14 03:32:24
● 2017-02-07 09:29:38
○ 2026-02-28 13:31:22
○ 2026-03-23 17:35:48
● 2015-11-14 03:32:24
● 2017-02-07 09:29:38
○ 2026-02-28 13:31:22
○ 2026-03-23 17:35:48
○NSns-cloud-e4.googledomains.com2015-11-14 → 2017-02-07 · 5 obs
○ 2015-06-05 12:47:50
● 2015-11-14 03:32:24
● 2017-02-07 09:29:38
○ 2026-02-28 13:31:22
○ 2026-03-23 17:35:48
● 2015-11-14 03:32:24
● 2017-02-07 09:29:38
○ 2026-02-28 13:31:22
○ 2026-03-23 17:35:48
●NSns31.domaincontrol.com2026-02-28 → 2026-03-23 · 3 obs
○ 2017-02-07 09:29:38
● 2026-02-28 13:31:22
● 2026-03-23 17:35:48
● 2026-02-28 13:31:22
● 2026-03-23 17:35:48
●NSns32.domaincontrol.com2026-02-28 → 2026-03-23 · 3 obs
○ 2017-02-07 09:29:38
● 2026-02-28 13:31:22
● 2026-03-23 17:35:48
● 2026-02-28 13:31:22
● 2026-03-23 17:35:48
○NSns8.wixdns.net2015-06-05 → 2015-06-05 · 3 obs
● 2015-06-05 12:47:50
○ 2015-11-14 03:32:24
○ 2026-03-23 17:35:48
○ 2015-11-14 03:32:24
○ 2026-03-23 17:35:48
○NSns9.wixdns.net2015-06-05 → 2015-06-05 · 3 obs
● 2015-06-05 12:47:50
○ 2015-11-14 03:32:24
○ 2026-03-23 17:35:48
○ 2015-11-14 03:32:24
○ 2026-03-23 17:35:48
○MXalt1.gmr-smtp-in.l.google.com2017-02-07 → 2017-02-07 · 3 obs
● 2017-02-07 09:29:38
○ 2026-02-28 13:31:22
○ 2026-03-23 17:35:48
○ 2026-02-28 13:31:22
○ 2026-03-23 17:35:48
○MXalt2.gmr-smtp-in.l.google.com2017-02-07 → 2017-02-07 · 3 obs
● 2017-02-07 09:29:38
○ 2026-02-28 13:31:22
○ 2026-03-23 17:35:48
○ 2026-02-28 13:31:22
○ 2026-03-23 17:35:48
○MXalt3.gmr-smtp-in.l.google.com2017-02-07 → 2017-02-07 · 3 obs
● 2017-02-07 09:29:38
○ 2026-02-28 13:31:22
○ 2026-03-23 17:35:48
○ 2026-02-28 13:31:22
○ 2026-03-23 17:35:48
○MXalt4.gmr-smtp-in.l.google.com2017-02-07 → 2017-02-07 · 3 obs
● 2017-02-07 09:29:38
○ 2026-02-28 13:31:22
○ 2026-03-23 17:35:48
○ 2026-02-28 13:31:22
○ 2026-03-23 17:35:48
○MXgmr-smtp-in.l.google.com2017-02-07 → 2017-02-07 · 3 obs
● 2017-02-07 09:29:38
○ 2026-02-28 13:31:22
○ 2026-03-23 17:35:48
○ 2026-02-28 13:31:22
○ 2026-03-23 17:35:48
○A23.236.62.1472015-06-05 → 2017-02-07 · 4 obs
● 2015-06-05 12:47:50
● 2017-02-07 09:29:38
○ 2020-01-19 01:03:50
○ 2026-03-23 17:35:48
● 2017-02-07 09:29:38
○ 2020-01-19 01:03:50
○ 2026-03-23 17:35:48
○A74.220.199.62020-01-19 → 2020-01-19 · 4 obs
○ 2017-02-07 09:29:38
● 2020-01-19 01:03:50
○ 2026-02-28 13:31:22
○ 2026-03-23 17:35:48
● 2020-01-19 01:03:50
○ 2026-02-28 13:31:22
○ 2026-03-23 17:35:48
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| technicallygeli.com | ns31.domaincontrol.com, ns32.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:97.74.105.16
NS records: ns31.domaincontrol.com, ns32.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for technicallygeli.com (unsigned zone)
⏱️ Timing
Total: 261ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | ns31.domaincontrol.com, ns32.domaincontrol.com |
| SOA | 1 | ns31.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns31.domaincontrol.com, ns31.domaincontrol.com, ns32.domaincontrol.com...)
Analysis
Name Servers
technicallygeli.com's delegation is to two name servers ns31.domaincontrol.com and ns32.domaincontrol.com.
technicallygeli.com shares the same name server configuration as other domains, such as corporate-housing-houston.com, bis-service.com, malamuchacha.com, orbrands.com and sugarlandacandheating.com.
Host names with two IP numbers: ns31.domaincontrol.com points to 2603:5:2191::10 and 97.74.105.16; ns32.domaincontrol.com points to 2603:5:2291::10 and 173.201.73.16