turingsaas.com - robtex.com
turingsaas.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=1783228816 | ||||||
Same first word
turingsaas.com |
Similar names
DNS History
24 records (12 active, 12 former)
●NSns-1340.awsdns-39.org2026-05-31 → 2026-07-05 · 3 obs
● 2026-05-31 18:23:46
● 2026-07-05 05:26:12
●NSns-1927.awsdns-48.co.uk2026-05-31 → 2026-07-05 · 3 obs
● 2026-05-31 18:23:46
● 2026-07-05 05:26:12
●NSns-194.awsdns-24.com2026-05-31 → 2026-07-05 · 3 obs
● 2026-05-31 18:23:46
● 2026-07-05 05:26:12
●NSns-946.awsdns-54.net2026-05-31 → 2026-07-05 · 3 obs
● 2026-05-31 18:23:46
● 2026-07-05 05:26:12
○NSpdns1.registrar-servers.com2019-03-27 → 2019-03-27 · 3 obs
○ 2026-05-31 18:23:46
○ 2026-07-05 05:26:12
○NSpdns2.registrar-servers.com2019-03-27 → 2019-03-27 · 3 obs
○ 2026-05-31 18:23:46
○ 2026-07-05 05:26:12
●MX5w6hua6z3looycjapnrzkm3772hvwaif27i55cpgahnccgizupdq.mx-verification.google.com2026-05-31 → 2026-07-05 · 3 obs
● 2026-05-31 18:23:46
● 2026-07-05 05:26:12
●MXalt1.aspmx.l.google.com2026-05-31 → 2026-07-05 · 3 obs
● 2026-05-31 18:23:46
● 2026-07-05 05:26:12
●MXalt2.aspmx.l.google.com2026-05-31 → 2026-07-05 · 3 obs
● 2026-05-31 18:23:46
● 2026-07-05 05:26:12
●MXalt3.aspmx.l.google.com2026-05-31 → 2026-07-05 · 3 obs
● 2026-05-31 18:23:46
● 2026-07-05 05:26:12
●MXalt4.aspmx.l.google.com2026-05-31 → 2026-07-05 · 3 obs
● 2026-05-31 18:23:46
● 2026-07-05 05:26:12
●MXaspmx.l.google.com2026-05-31 → 2026-07-05 · 3 obs
● 2026-05-31 18:23:46
● 2026-07-05 05:26:12
○MXeforward1.registrar-servers.com2019-03-27 → 2019-03-27 · 3 obs
○ 2026-05-31 18:23:46
○ 2026-07-05 05:26:12
○MXeforward2.registrar-servers.com2019-03-27 → 2019-03-27 · 3 obs
○ 2026-05-31 18:23:46
○ 2026-07-05 05:26:12
○MXeforward3.registrar-servers.com2019-03-27 → 2019-03-27 · 3 obs
○ 2026-05-31 18:23:46
○ 2026-07-05 05:26:12
○MXeforward4.registrar-servers.com2019-03-27 → 2019-03-27 · 3 obs
○ 2026-05-31 18:23:46
○ 2026-07-05 05:26:12
○MXeforward5.registrar-servers.com2019-03-27 → 2019-03-27 · 3 obs
○ 2026-05-31 18:23:46
○ 2026-07-05 05:26:12
●MXms92478906.msv1.invalid2026-05-31 → 2026-07-05 · 3 obs
● 2026-05-31 18:23:46
● 2026-07-05 05:26:12
○A13.248.155.1042026-05-31 → 2026-05-31 · 3 obs
● 2026-05-31 18:23:46
○ 2026-07-05 05:26:12
○A192.64.119.2012019-03-27 → 2019-03-27 · 3 obs
○ 2026-05-31 18:23:46
○ 2026-07-05 05:26:12
●A207.207.209.2092026-07-05 → 2026-07-05 · 2 obs
● 2026-07-05 05:26:12
○A75.2.70.752026-05-31 → 2026-05-31 · 3 obs
● 2026-05-31 18:23:46
○ 2026-07-05 05:26:12
○A76.223.27.1022026-05-31 → 2026-05-31 · 3 obs
● 2026-05-31 18:23:46
○ 2026-07-05 05:26:12
○A99.83.190.1022026-05-31 → 2026-05-31 · 3 obs
● 2026-05-31 18:23:46
○ 2026-07-05 05:26:12
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | k.gtld-servers.net, d.gtld-servers.net, h.gtld-servers.net, l.gtld-servers.net... | - |
| turingsaas.com | ns-194.awsdns-24.com, ns-946.awsdns-54.net, ns-1927.awsdns-48.co.uk, ns-1340.awsdns-39.org | 2 records |
✅ Authoritative Response
Server:205.251.199.135
NS records: ns-194.awsdns-24.com, ns-946.awsdns-54.net, ns-1927.awsdns-48.co.uk, ns-1340.awsdns-39.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for turingsaas.com (unsigned zone)
⏱️ Timing
Total: 283ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 207.207.209.209 |
| NS | 4 | ns-1340.awsdns-39.org, ns-1927.awsdns-48.co.uk... |
| MX | 7 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 6 | _fs87id9041tx7xzihbzdrpyv3twaenq, amazonses:iHBTwX9ktoeIfxUfOozfEpViTwoawU... |
| SOA | 1 | ns-1340.awsdns-39.org awsdns-hostmaster. |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns-194.awsdns-24.com, ns-194.awsdns-24.com)
Analysis
IP Addresses
turingsaas.com has exactly one IP address — 207.207.209.209.
superunit.com, vectoral.com, attention.tech plus two other host names have IP numbers in common with turingsaas.com.
Name Servers
Four name servers handle the delegation for turingsaas.com: ns-194.awsdns-24.com, ns-946.awsdns-54.net, ns-1340.awsdns-39.org and ns-1927.awsdns-48.co.uk.
turingsaas.com has at least partial name server overlap with other domains, such as livesafeedu.com, cerrapoints.com, mint777.com and two others.
ns-194.awsdns-24.com, ns-946.awsdns-54.net, ns-1340.awsdns-39.org and ns-1927.awsdns-48.co.uk all point to exactly two IP numbers each: ns-194.awsdns-24.com → 205.251.192.194 and 2600:9000:5300:c200::1; ns-946.awsdns-54.net → 205.251.195.178 and 2600:9000:5303:b200::1; ns-1340.awsdns-39.org → 205.251.197.60 and 2600:9000:5305:3c00::1; ns-1927.awsdns-48.co.uk → 205.251.199.135 and 2600:9000:5307:8700::1.
Mail Servers
Mail for turingsaas.com is routed through 7 mail servers, including ms92478906.msv1.invalid, aspmx.l.google.com, 5w6hua6z3looycjapnrzkm3772hvwaif27i55cpgahnccgizupdq.mx-verification.google.com and 4 other.
At least some of the mail servers used by turingsaas.com are shared with other domains: ns500724.ns500724.ns500724.ns500599.ns500724.ns500724.ns500599.ns500599.ns500724.ns500737.ns500583.ns500697.ns500697.www.yummyflingsfinder.com, littlemowine.com, ns500765.ns500699.ns500734.ns500693.ns500734.ns500693.ns500588.ns500699.ns500693.ns500683.ns500632.ns500632.ns500632.ns500110.dtrkdll.com and two others among them.
These mail servers are often deployed together with alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 other mail servers.
Host names pointing to two IP addresses:
aspmx.l.google.com resolves to 172.253.122.26 and 2607:f8b0:4004:c23::1a.
alt1.aspmx.l.google.com resolves to 108.177.123.27 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com resolves to 172.253.116.27 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com resolves to 192.178.223.27 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com resolves to 172.253.157.26 and 2a00:1450:400c:c23::1a.