teamworkwave.com - robtex.com
teamworkwave.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=1771291435 | ||||||
Same first word
teamworkwave.com |
DNS History
9 records (9 active, 0 former)
●NSns1-04.azure-dns.com2026-02-24 → 2026-03-22 · 2 obs
● 2026-03-22 14:58:28
●NSns2-04.azure-dns.net2026-02-24 → 2026-03-22 · 2 obs
● 2026-03-22 14:58:28
●NSns3-04.azure-dns.org2026-02-24 → 2026-03-22 · 2 obs
● 2026-03-22 14:58:28
●NSns4-04.azure-dns.info2026-02-24 → 2026-03-22 · 2 obs
● 2026-03-22 14:58:28
●MXalt1.aspmx.l.google.com2026-02-24 → 2026-03-22 · 2 obs
● 2026-03-22 14:58:28
●MXalt2.aspmx.l.google.com2026-02-24 → 2026-03-22 · 2 obs
● 2026-03-22 14:58:28
●MXalt3.aspmx.l.google.com2026-02-24 → 2026-03-22 · 2 obs
● 2026-03-22 14:58:28
●MXalt4.aspmx.l.google.com2026-02-24 → 2026-03-22 · 2 obs
● 2026-03-22 14:58:28
●MXaspmx.l.google.com2026-02-24 → 2026-03-22 · 2 obs
● 2026-03-22 14:58:28
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | m.gtld-servers.net, j.gtld-servers.net, d.gtld-servers.net, f.gtld-servers.net... | - |
| teamworkwave.com | ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info | 2 records |
✅ Authoritative Response
Server: 13.107.236.4
NS records: ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for teamworkwave.com (unsigned zone)
⏱️ Timing
Total: 436ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns1-04.azure-dns.com, ns2-04.azure-dns.net... |
| MX | 5 | aspmx.l.google.com (pri: 0), alt1.aspmx.l.google.com (pri: 10)... |
| TXT | 1 | v=spf1 include:_spf.google.com include:s |
| SOA | 1 | ns1-04.azure-dns.com hostmaster.teamwork |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1-04.azure-dns.com, ns1-04.azure-dns.com)
Analysis
Name Servers
teamworkwave.com is delegated to four name servers: ns1-04.azure-dns.com, ns4-04.azure-dns.info, ns2-04.azure-dns.net and ns3-04.azure-dns.org.
teamworkwave.com at least partially shares name servers with other domains, including sapphiresvc.com, aryinc.com, stjosephswbclinic.com, ifpn.com.br and audiostarpro.com.
Hosts with two IP numbers:
Host ns1-04.azure-dns.com points to 2603:1061:0:700::4 and 13.107.236.4
Host ns4-04.azure-dns.info points to 2620:1ec:bda:700::4 and 208.84.5.4
Host ns2-04.azure-dns.net points to 2620:1ec:8ec:700::4 and 150.171.21.4
Host ns3-04.azure-dns.org points to 2a01:111:4000:700::4 and 204.14.183.4
Mail Servers
teamworkwave.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.
The mail servers for teamworkwave.com are shared with other domains, for instance senia.com, ns500794.ns500794.ns500794.ns500794.ns500794.ns500821.ns500790.lustypartnersfinder.com, lanouvellegarde.com, btacapital.com.co and ns500742.ns500731.ns500754.ns500742.ns500742.ns500688.ns500678.ns500688.ns500705.ns500666.ns500291.ns500131.lustychickser.com.
These mail servers are commonly used alongside aspmx3.googlemail.com and aspmx2.googlemail.com.
Host names with two IP numbers:
aspmx.l.google.com points to 2607:f8b0:4004:c19::1b and 172.253.62.27.
alt1.aspmx.l.google.com points to 2607:f8b0:4003:c30::1b and 74.125.27.26.
alt2.aspmx.l.google.com points to 2607:f8b0:4001:c70::1a and 192.178.209.26.
alt3.aspmx.l.google.com points to 2607:f8b0:4024:c0d::1b and 192.178.152.26.
alt4.aspmx.l.google.com points to 2607:f8b0:4023:403::1a and 142.250.96.27.