complete.so - dns.ninja
complete.so
so
| DNSSEC | ⚠️ Not signed | ||||||
| NS | d.nic.so ⭐ | ||||||
| NS | e.nic.so | ||||||
| TXT | Generation Time ISO 8601: 2026-08-05 04:00:04 | ||||||
| TXT | Generation Time: 1785902404 | ||||||
| SOA | d.nic.sohostmaster@nic.so 2026-08-05 #4 | ||||||
Same first word
Similar names
DNS History
8 records (8 active, 0 former)
●NSdns1.registrar-servers.com2026-03-31 → 2026-08-05 · 2 obs
● 2026-08-05 04:39:32
●NSdns2.registrar-servers.com2026-03-31 → 2026-08-05 · 2 obs
● 2026-08-05 04:39:32
●MXalt1.aspmx.l.google.com2026-03-31 → 2026-08-05 · 2 obs
● 2026-08-05 04:39:32
●MXalt2.aspmx.l.google.com2026-03-31 → 2026-08-05 · 2 obs
● 2026-08-05 04:39:32
●MXaspmx.l.google.com2026-03-31 → 2026-08-05 · 2 obs
● 2026-08-05 04:39:32
●MXaspmx2.googlemail.com2026-03-31 → 2026-08-05 · 2 obs
● 2026-08-05 04:39:32
●MXaspmx3.googlemail.com2026-03-31 → 2026-08-05 · 2 obs
● 2026-08-05 04:39:32
●A198.202.211.12026-03-31 → 2026-08-05 · 2 obs
● 2026-08-05 04:39:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| so | d.nic.so, e.nic.so | 4 records |
| complete.so | dns1.registrar-servers.com, dns2.registrar-servers.com | - |
✅ Authoritative Response
Server:156.154.132.200
NS records: dns1.registrar-servers.com, dns2.registrar-servers.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for so (unsigned zone)
⏱️ Timing
Total: 384ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 198.202.211.1 |
| NS | 2 | dns1.registrar-servers.com, dns2.registrar-servers.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 5 | proxy-ssl.webflow.com, v=spf1 include:_spf.google.com ~all... |
| SOA | 1 | dns1.registrar-servers.com hostmaster.re |
📌 Glue Records Collected
Total: 4
In-bailiwick: 4 (d.nic.so, e.nic.so, d.nic.so...)
Analysis
IP Addresses
complete.so resolves to just one IP address, 198.202.211.1.
Two other host names, along with watchduty.org, pushgroup.ae and bpeace.com, also share IP numbers with complete.so.
Name Servers
complete.so is delegated to two name servers: dns1.registrar-servers.com and dns2.registrar-servers.com.
complete.so shares its NS records with other domains, for example zamanjewellers.com, indianapolisdirectory.org, kokoworks.com and two others.
complete.so has a partial name server overlap with other domains — among them dtsorbit.com and teletweetapp.com.
dns1.registrar-servers.com and dns2.registrar-servers.com each resolve to two IP addresses: dns1.registrar-servers.com points to 156.154.132.200 and 2610:a1:1024::200, while dns2.registrar-servers.com points to 156.154.133.200 and 2610:a1:1025::200.
Mail Servers
complete.so is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
There is at least a partial MX overlap between complete.so and other domains, including capnet.org, ns500759.ns500758.ns500758.ns500759.ns500735.ns500698.ns500736.ns500698.ns500708.ns500576.ns500619.ns500576.ns500576.ns500652.trackreceptor.com, ns500671.ns500731.ns500731.ns500754.ns500742.ns500731.ns500688.ns500291.ns500678.ns500291.ns500671.ns500666.ns500153.tenderladiesbz.com and two others.
These mail servers tend to appear in combination with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.
Host names that have two IP addresses:
aspmx2.googlemail.com points to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
aspmx3.googlemail.com points to 172.253.116.26 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com points to 173.194.45.26 and 2607:f8b0:4004:c09::1b.
alt1.aspmx.l.google.com points to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com points to 172.253.116.27 and 2a00:1450:400b:c02::1b.
aspmx2.googlemail.com and alt1.aspmx.l.google.com are host names that each point to 2800:3f0:4003:c0f::1a IP addresses.
aspmx2.googlemail.com and alt1.aspmx.l.google.com are host names that each point to 108.177.123.26 IP addresses.