aifield.com - dns.ninja
aifield.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=1785446167 | ||||||
Previously NS for
aifield.com |
Previously MX for
aifield.com |
Same first word
Similar names
DNS History
9 records (6 active, 3 former)
○NSaifield.com2015-06-18 → 2017-07-03 · 4 obs
● 2017-07-03 06:18:56
○ 2026-02-16 10:29:16
○ 2026-07-30 21:16:58
●NSns1.name.com2026-02-16 → 2026-07-30 · 3 obs
● 2026-02-16 10:29:16
● 2026-07-30 21:16:58
●NSns1kwy.name.com2026-02-16 → 2026-07-30 · 3 obs
● 2026-02-16 10:29:16
● 2026-07-30 21:16:58
●NSns2kry.name.com2026-02-16 → 2026-07-30 · 3 obs
● 2026-02-16 10:29:16
● 2026-07-30 21:16:58
●NSns3bfm.name.com2026-02-16 → 2026-07-30 · 3 obs
● 2026-02-16 10:29:16
● 2026-07-30 21:16:58
●NSns4htz.name.com2026-02-16 → 2026-07-30 · 3 obs
● 2026-02-16 10:29:16
● 2026-07-30 21:16:58
○MXaifield.com2015-06-18 → 2026-02-16 · 4 obs
● 2026-02-16 10:29:16
○ 2026-02-19 10:19:36
○ 2026-07-30 21:16:58
○A202.218.234.1702015-06-18 → 2017-07-03 · 4 obs
● 2017-07-03 06:18:56
○ 2026-02-16 10:29:16
○ 2026-07-30 21:16:58
●A75.126.104.2422026-02-16 → 2026-07-30 · 3 obs
● 2026-02-16 10:29:16
● 2026-07-30 21:16:58
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| aifield.com | ns1kwy.name.com, ns2kry.name.com, ns3bfm.name.com, ns4htz.name.com | 8 records |
✅ Authoritative Response
Server:163.114.217.49
NS records: ns1kwy.name.com, ns2kry.name.com, ns3bfm.name.com, ns4htz.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for aifield.com (unsigned zone)
⏱️ Timing
Total: 274ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 75.126.104.242 |
| NS | 4 | ns1kwy.name.com, ns2kry.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns1kwy.name.com, ns1kwy.name.com, ns2kry.name.com...)
Analysis
IP Addresses
aifield.com resolves to just one IP address, 75.126.104.242.
Two other host names, along with youdropwefix.com, mx.katzenbergers.com and williamdenton.com, also share IP numbers with aifield.com.
Name Servers
aifield.com delegates to five name servers: ns1.name.com, ns1kwy.name.com, ns2kry.name.com and two others.
At least some of aifield.com's name servers are shared with other domains, for example 901004.com, tam.enterprises, castlovespell.com and two more.
These name servers tend to co-occur with ns3bfm.name.com, ns4htz.name.com, ns1cny.name.com and 7 other name servers in the same DNS delegations.
Host names that have two IP addresses:
ns1.name.com resolves to two addresses: 163.114.216.17 and 2a00:edc0:107::1.
ns1kwy.name.com resolves to two addresses: 163.114.216.17 and 2a00:edc0:107::1.
ns2kry.name.com resolves to two addresses: 163.114.216.49 and 2402:cf80:107::1.
ns3bfm.name.com resolves to two addresses: 163.114.217.17 and 2a00:edc0:107::49.
ns4htz.name.com resolves to two addresses: 163.114.217.49 and 2402:cf80:107::49.
ns1.name.com along with ns1kwy.name.com each resolve to 2a00:edc0:107::1 IP addresses.
ns1.name.com along with ns1kwy.name.com each resolve to 163.114.216.17 IP addresses.