threadfoundry.com - dns.ninja
threadfoundry.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=1791680524 | ||||||
Same first word
threadfoundry.au |
threadfoundry.com |
threadfoundry.dev |
threadfoundry.co |
threadfoundry.cfd |
threadfoundry.org |
threadfoundry.shop |
threadfoundry.app |
Similar names
Previous names
Next names
DNS History
19 records (9 active, 10 former)
○NSns1.undeveloped.com2019-01-08 → 2019-01-08 · 4 obs
● 2019-01-08 00:52:08
○ 2026-09-30 08:23:04
○ 2026-10-11 03:31:24
○NSns2.undeveloped.com2019-01-08 → 2019-01-08 · 4 obs
● 2019-01-08 00:52:08
○ 2026-09-30 08:23:04
○ 2026-10-11 03:31:24
●NSns41.domaincontrol.com2026-09-30 → 2026-10-11 · 3 obs
● 2026-09-30 08:23:04
● 2026-10-11 03:31:24
●NSns42.domaincontrol.com2026-09-30 → 2026-10-11 · 3 obs
● 2026-09-30 08:23:04
● 2026-10-11 03:31:24
○NSns65.domaincontrol.com2015-06-22 → 2017-02-02 · 4 obs
● 2017-02-02 14:22:16
○ 2019-01-08 00:52:08
○ 2026-10-11 03:31:24
○NSns66.domaincontrol.com2015-06-22 → 2017-02-02 · 4 obs
● 2017-02-02 14:22:16
○ 2019-01-08 00:52:08
○ 2026-10-11 03:31:24
●MXalt1.aspmx.l.google.com2026-09-30 → 2026-10-11 · 3 obs
● 2026-09-30 08:23:04
● 2026-10-11 03:31:24
●MXalt2.aspmx.l.google.com2026-09-30 → 2026-10-11 · 3 obs
● 2026-09-30 08:23:04
● 2026-10-11 03:31:24
●MXalt3.aspmx.l.google.com2026-09-30 → 2026-10-11 · 3 obs
● 2026-09-30 08:23:04
● 2026-10-11 03:31:24
●MXalt4.aspmx.l.google.com2026-09-30 → 2026-10-11 · 3 obs
● 2026-09-30 08:23:04
● 2026-10-11 03:31:24
●MXaspmx.l.google.com2026-09-30 → 2026-10-11 · 3 obs
● 2026-09-30 08:23:04
● 2026-10-11 03:31:24
○MXmailstore1.secureserver.net2015-06-22 → 2017-02-02 · 4 obs
● 2017-02-02 14:22:16
○ 2019-01-08 00:52:08
○ 2026-10-11 03:31:24
○MXmx.threadfoundry.com2019-01-08 → 2019-01-08 · 4 obs
● 2019-01-08 00:52:08
○ 2026-09-30 08:23:04
○ 2026-10-11 03:31:24
○MXsmtp.secureserver.net2015-06-22 → 2017-02-02 · 4 obs
● 2017-02-02 14:22:16
○ 2019-01-08 00:52:08
○ 2026-10-11 03:31:24
●A15.197.148.332026-09-30 → 2026-10-11 · 3 obs
● 2026-09-30 08:23:04
● 2026-10-11 03:31:24
○A23.227.38.322015-06-22 → 2017-02-02 · 4 obs
● 2017-02-02 14:22:16
○ 2019-01-08 00:52:08
○ 2026-10-11 03:31:24
○A2a05:d014:9da:8c10:306e:3e07:a16f:a5522019-01-08 → 2019-01-08 · 4 obs
● 2019-01-08 00:52:08
○ 2026-09-30 08:23:04
○ 2026-10-11 03:31:24
●A3.33.130.1902026-09-30 → 2026-10-11 · 3 obs
● 2026-09-30 08:23:04
● 2026-10-11 03:31:24
○A52.58.78.162019-01-08 → 2019-01-08 · 4 obs
● 2019-01-08 00:52:08
○ 2026-09-30 08:23:04
○ 2026-10-11 03:31:24
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | k.gtld-servers.net, c.gtld-servers.net, l.gtld-servers.net, e.gtld-servers.net... | - |
| threadfoundry.com | ns41.domaincontrol.com, ns42.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.68.21
NS records: ns41.domaincontrol.com, ns42.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for threadfoundry.com (unsigned zone)
⏱️ Timing
Total: 495ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 3.33.130.190, 15.197.148.33 |
| NS | 2 | ns41.domaincontrol.com, ns42.domaincontrol.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| TXT | 2 | v=spf1 include:dc-aa8e722993._spfm.threa, google-site-verification=vifDXNrCgFyFNAC |
| SOA | 1 | ns41.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns41.domaincontrol.com, ns41.domaincontrol.com, ns42.domaincontrol.com...)
Analysis
IP Addresses
threadfoundry.com resolves to the IP addresses 3.33.130.190 and 15.197.148.33
Two other host names, along with travelprobook.com, sagevisioneering.com and indara-tech.com, also share IP numbers with threadfoundry.com.
Name Servers
threadfoundry.com is delegated to two name servers: ns41.domaincontrol.com and ns42.domaincontrol.com.
threadfoundry.com shares its NS records with other domains, for example velorasource.com, pxlab.com.br, lackoflifestyle.biz and two others.
ns41.domaincontrol.com and ns42.domaincontrol.com each resolve to two IP addresses: ns41.domaincontrol.com points to 97.74.100.21 and 2603:5:2142::15, while ns42.domaincontrol.com points to 173.201.68.21 and 2603:5:2242::15.
Mail Servers
threadfoundry.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
There is at least a partial MX overlap between threadfoundry.com and other domains, including neuralgrain.com, peninsulamachine.com, echoarch.net and two others.
alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com are mail servers that frequently appear together with these mail servers.
Host names that have two IP addresses:
aspmx.l.google.com points to 64.233.180.26 and 2607:f8b0:4004:c2f::1b.
alt1.aspmx.l.google.com points to 192.178.234.26 and 2800:3f0:4003:c14::1a.
alt2.aspmx.l.google.com points to 172.253.116.26 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com points to 192.178.223.26 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com points to 172.253.157.26 and 2a00:1450:400c:c23::1b.