taskforceplus.com - robtex.com
taskforceplus.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=1794606381 | ||||||
Same first word
taskforceplus.com |
Previous names
Next names
DNS History
8 records (8 active, 0 former)
●NSns31.domaincontrol.com2026-09-10 → 2026-11-13 · 2 obs
● 2026-11-13 22:04:58
●NSns32.domaincontrol.com2026-09-10 → 2026-11-13 · 2 obs
● 2026-11-13 22:04:58
●MXalt1.aspmx.l.google.com2026-09-10 → 2026-11-13 · 2 obs
● 2026-11-13 22:04:58
●MXalt2.aspmx.l.google.com2026-09-10 → 2026-11-13 · 2 obs
● 2026-11-13 22:04:58
●MXalt3.aspmx.l.google.com2026-09-10 → 2026-11-13 · 2 obs
● 2026-11-13 22:04:58
●MXalt4.aspmx.l.google.com2026-09-10 → 2026-11-13 · 2 obs
● 2026-11-13 22:04:58
●MXaspmx.l.google.com2026-09-10 → 2026-11-13 · 2 obs
● 2026-11-13 22:04:58
●A188.245.111.352026-09-10 → 2026-11-13 · 2 obs
● 2026-11-13 22:04: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... | - |
| taskforceplus.com | ns31.domaincontrol.com, ns32.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.73.16
NS records: ns31.domaincontrol.com, ns32.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
Root DNSKEY fetch failed: Error: connect EADDRNOTAVAIL 198.41.0.4:53 - Local (0.0.0.0:0)
⏱️ Timing
Total: 911ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 188.245.111.35 |
| NS | 2 | ns31.domaincontrol.com, ns32.domaincontrol.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 2 | google-site-verification=RD6AgtGyefCzPQD, v=spf1 a mx include:dc-aa8e722993._spfm. |
| 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
IP Addresses
taskforceplus.com resolves to one IP address: 188.245.111.35.
lonestardads.com, for instance, is one of the other host names sharing IP numbers with taskforceplus.com.
Name Servers
taskforceplus.com uses two name servers for its delegation: ns31.domaincontrol.com and ns32.domaincontrol.com.
taskforceplus.com uses the same name servers as several other domains — among them invidiagroup.com.au, blackpoint.limo, sonofdustltd.com and two more.
The two host names ns31.domaincontrol.com and ns32.domaincontrol.com each have a pair of IP addresses: ns31.domaincontrol.com has 97.74.105.16 and 2603:5:2191::10, and ns32.domaincontrol.com has 173.201.73.16 and 2603:5:2291::10.
Mail Servers
taskforceplus.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
taskforceplus.com has at least partial mail server overlap with other domains such as carmelarchitecturalmillwork.com, baldydog.com, summitconflictsolutions.com and two more.
These mail servers commonly co-occur with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.
Hostnames that resolve to two IP addresses:
aspmx.l.google.com directs traffic to 172.217.75.27 and 2607:f8b0:4023:200b::1a.
alt1.aspmx.l.google.com directs traffic to 192.178.234.27 and 2800:3f0:4003:c14::1b.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com directs traffic to 192.178.223.27 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com directs traffic to 172.253.157.26 and 2a00:1450:400c:c23::1b.