wouldworks.com - dns.ninja
wouldworks.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=1786013904 | ||||||
Same first word
wouldworks.com |
DNS History
12 records (8 active, 4 former)
○NSns.wouldworks.com2016-07-21 → 2016-07-21 · 3 obs
○ 2017-09-13 12:08:58
○ 2026-08-06 10:58:56
●NSns27.domaincontrol.com2017-09-13 → 2026-08-06 · 3 obs
● 2017-09-13 12:08:58
● 2026-08-06 10:58:56
●NSns28.domaincontrol.com2017-09-13 → 2026-08-06 · 3 obs
● 2017-09-13 12:08:58
● 2026-08-06 10:58:56
●MXalt1.aspmx.l.google.com2017-09-13 → 2026-08-06 · 2 obs
● 2026-08-06 10:58:56
●MXalt2.aspmx.l.google.com2017-09-13 → 2026-08-06 · 2 obs
● 2026-08-06 10:58:56
●MXalt3.aspmx.l.google.com2017-09-13 → 2026-08-06 · 2 obs
● 2026-08-06 10:58:56
●MXalt4.aspmx.l.google.com2017-09-13 → 2026-08-06 · 2 obs
● 2026-08-06 10:58:56
●MXaspmx.l.google.com2017-09-13 → 2026-08-06 · 2 obs
● 2026-08-06 10:58:56
○A128.136.35.262015-06-04 → 2015-06-04 · 3 obs
○ 2015-10-30 15:18:06
○ 2026-08-06 10:58:56
○A141.8.225.1132015-10-30 → 2016-03-13 · 5 obs
● 2015-10-30 15:18:06
● 2016-03-13 04:48:38
○ 2016-07-21 08:21:08
○ 2026-08-06 10:58:56
●A23.227.38.322017-09-13 → 2026-08-06 · 3 obs
● 2017-09-13 12:08:58
● 2026-08-06 10:58:56
○A91.195.241.722016-07-21 → 2016-07-21 · 4 obs
● 2016-07-21 08:21:08
○ 2017-09-13 12:08:58
○ 2026-08-06 10:58:56
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | i.gtld-servers.net, d.gtld-servers.net, g.gtld-servers.net, b.gtld-servers.net... | - |
| wouldworks.com | ns27.domaincontrol.com, ns28.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.71.14
NS records: ns27.domaincontrol.com, ns28.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for wouldworks.com (unsigned zone)
⏱️ Timing
Total: 230ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 23.227.38.32 |
| NS | 2 | ns27.domaincontrol.com, ns28.domaincontrol.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 1 | google-site-verification=mNc5_3B0XFBDKn0 |
| SOA | 1 | ns27.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns27.domaincontrol.com, ns27.domaincontrol.com, ns28.domaincontrol.com...)
Analysis
IP Addresses
wouldworks.com has exactly one IP address — 23.227.38.32.
sweetsallie.com, bad-elf.com, frankieandclaude.com plus two other host names have IP numbers in common with wouldworks.com.
Name Servers
Two name servers handle the delegation for wouldworks.com: ns27.domaincontrol.com and ns28.domaincontrol.com.
The name server configuration of wouldworks.com is shared with other domains, for instance gza888.com, vimc.net, cashflowexperience.com and two others.
wouldworks.com is at least partially co-delegated on name servers with other domains, such as lumisave.com.
ns27.domaincontrol.com and ns28.domaincontrol.com both carry two IP addresses. The A records for ns27.domaincontrol.com are 97.74.103.14 and 2603:5:2171::e; the A records for ns28.domaincontrol.com are 173.201.71.14 and 2603:5:2271::e.
Mail Servers
wouldworks.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
At least some of the mail servers used by wouldworks.com are shared with other domains: ns500731.ns500754.ns500754.ns500705.ns500704.ns500671.ns500678.ns500704.ns500678.ns500678.ns500291.ns500291.ns500291.ns500291.ns500291.ns500131.lustychickser.com, ns500759.ns500698.ns500759.ns500698.ns500698.ns500698.ns500735.ns500735.ns500736.ns500736.ns500736.ns500708.ns500698.ns500619.ns500576.ns500576.trackreceptor.com, ns500758.ns500698.ns500758.ns500759.ns500758.ns500698.ns500735.ns500735.ns500735.ns500736.ns500698.ns500698.ns500619.ns500619.trackreceptor.com and two others among them.
These mail servers often appear in conjunction with the mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com.
Host names pointing to two IP addresses:
aspmx.l.google.com resolves to two addresses: 173.194.45.26 and 2607:f8b0:4004:c25::1b.
alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.27 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.26 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com resolves to two addresses: 192.178.223.27 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com resolves to two addresses: 172.253.157.27 and 2a00:1450:400c:c23::1b.