teamcommand.net - dns.ninja
teamcommand.net
| DNSSEC | ⚠️ Not signed | ||||||
| A | 13.248.169.48🇺🇸 Amazon13.248.160.0/20 | ||||||
| PTR | a904c694c05102f30.awsglobalaccelerator.com | ||||||
| A | 76.223.54.146🇺🇸 Amazon76.223.48.0/20 | ||||||
| NS | ns1.afternic.com ⭐ | ||||||
| A | 2603:5:2126::45🇺🇸 GODADDY-DNS2603:5:2120::/44 | ||||||
| PTR | ns1.afternic.com | ||||||
| A | 97.74.98.69🇺🇸 GODADDY-DNS97.74.98.0/23 | ||||||
| PTR | ns1.afternic.com | ||||||
| NS | ns2.afternic.com | ||||||
| A | 2603:5:2226::45🇺🇸 GODADDY-DNS2603:5:2220::/44 | ||||||
| PTR | ns2.afternic.com | ||||||
| A | 173.201.66.69🇺🇸 GODADDY-DNS173.201.66.0/23 | ||||||
| PTR | ns2.afternic.com | ||||||
| NS | verification-k4ibaefv92b8mcahic8cdo.ns101.verify.hn ⚠️ Not in zone NS records | ||||||
| A | 13.248.169.48🇺🇸 Amazon13.248.160.0/20 | ||||||
| PTR | a904c694c05102f30.awsglobalaccelerator.com | ||||||
| A | 76.223.54.146🇺🇸 Amazon76.223.48.0/20 | ||||||
| TXT | v=spf1 -all | ||||||
| SOA | ns1.afternic.comdns@jomax.net serial=1 | ||||||
net
| 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=1793050531 | ||||||
Same first word
Similar names
commandmeta.com |
metacommand.io |
commandteam.com |
madamnetcom.lol |
metacommand.net |
metacommand.ai |
metacommand.com |
commandteam.xyz |
Previous names
Next names
DNS History
5 records (5 active, 0 former)
●NSns1.afternic.com2026-10-11 → 2026-10-26 · 2 obs
● 2026-10-26 21:46:58
●NSns2.afternic.com2026-10-11 → 2026-10-26 · 2 obs
● 2026-10-26 21:46:58
●NSverification-k4ibaefv92b8mcahic8cdo.ns101.verify.hn2026-10-11 → 2026-10-26 · 2 obs
● 2026-10-26 21:46:58
●A13.248.169.482026-10-11 → 2026-10-26 · 2 obs
● 2026-10-26 21:46:58
●A76.223.54.1462026-10-11 → 2026-10-26 · 2 obs
● 2026-10-26 21:46:58
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| net | k.gtld-servers.net, l.gtld-servers.net, e.gtld-servers.net, d.gtld-servers.net... | - |
| teamcommand.net | ns1.afternic.com, ns2.afternic.com, verification-k4ibaefv92b8mcahic8cdo.ns101.verify.hn | - |
✅ Authoritative Response
Server:97.74.98.69
NS records: ns1.afternic.com, ns2.afternic.com, verification-k4ibaefv92b8mcahic8cdo.ns101.verify.hn
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for teamcommand.net (unsigned zone)
⏱️ Timing
Total: 4856ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 76.223.54.146, 13.248.169.48 |
| NS | 2 | ns1.afternic.com, ns2.afternic.com |
| MX | 1 | . (pri: 0) |
| TXT | 1 | v=spf1 -all |
| SOA | 1 | ns1.afternic.com dns.jomax.net |
Analysis
IP Addresses
teamcommand.net directs to two IP numbers, 13.248.169.48 and 76.223.54.146
Among the host names that share IP numbers with teamcommand.net are strectchmarkremoval4u.publicsets.com, hackerbath.xyz, chiprich.xyz and two others.
Name Servers
Three name servers are authoritative for teamcommand.net: ns1.afternic.com, ns2.afternic.com and verification-k4ibaefv92b8mcahic8cdo.ns101.verify.hn.
teamcommand.net has at least partial name server overlap with other domains, such as boxetf.com, boete.com, sailapartments.com and two others.
It is common to find these name servers paired with the name servers verification-m3erh32ujyoastvophjvuz.ns101.verify.hn, verification-vesbet7nkettdw2mc9cgox.ns101.verify.hn, verification-e7ktf2ehupufe4sbe7xxk3.ns101.verify.hn and verification-d3jclucsp89ganyqbydeny.ns101.verify.hn.
ns1.afternic.com resolves to 97.74.98.69 and 2603:5:2126::45. ns2.afternic.com resolves to 173.201.66.69 and 2603:5:2226::45. verification-k4ibaefv92b8mcahic8cdo.ns101.verify.hn resolves to 13.248.169.48 and 76.223.54.146. All three hostnames point to two IP numbers each.