telements.com - dns.ninja
telements.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=1783053951 | ||||||
Same first word
telements.com |
Similar names
DNS History
9 records (8 active, 1 former)
●NSns21.domaincontrol.com2015-07-25 → 2026-07-03 · 2 obs
● 2026-07-03 04:56:12
●NSns22.domaincontrol.com2015-07-25 → 2026-07-03 · 2 obs
● 2026-07-03 04:56:12
●MXalt1.aspmx.l.google.com2015-07-25 → 2026-07-03 · 2 obs
● 2026-07-03 04:56:12
●MXalt2.aspmx.l.google.com2015-07-25 → 2026-07-03 · 2 obs
● 2026-07-03 04:56:12
●MXalt3.aspmx.l.google.com2015-07-25 → 2026-07-03 · 2 obs
● 2026-07-03 04:56:12
●MXalt4.aspmx.l.google.com2015-07-25 → 2026-07-03 · 2 obs
● 2026-07-03 04:56:12
●MXaspmx.l.google.com2015-07-25 → 2026-07-03 · 2 obs
● 2026-07-03 04:56:12
●A52.1.184.1402016-02-25 → 2026-07-03 · 3 obs
● 2016-02-25 00:29:12
● 2026-07-03 04:56:12
○A54.172.167.462015-07-25 → 2015-11-23 · 4 obs
● 2015-11-23 06:14:32
○ 2016-02-25 00:29:12
○ 2026-07-03 04:56:12
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | c.gtld-servers.net, m.gtld-servers.net, d.gtld-servers.net, k.gtld-servers.net... | - |
| telements.com | ns21.domaincontrol.com, ns22.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:97.74.100.11
NS records: ns21.domaincontrol.com, ns22.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for telements.com (unsigned zone)
⏱️ Timing
Total: 1017ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 52.1.184.140 |
| NS | 2 | ns21.domaincontrol.com, ns22.domaincontrol.com |
| MX | 5 | alt1.aspmx.l.google.com (pri: 5), alt2.aspmx.l.google.com (pri: 5)... |
| TXT | 2 | NETORGFT9931405.onmicrosoft.com, google-site-verification=jHSst8lnclIjmWO |
| SOA | 1 | ns21.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns21.domaincontrol.com, ns21.domaincontrol.com, ns22.domaincontrol.com...)
Analysis
IP Addresses
telements.com has exactly one IP address — 52.1.184.140.
ec2-52-1-184-140.compute-1.amazonaws.com, for instance, is one of the other host names sharing IP numbers with telements.com.
Name Servers
telements.com uses two name servers for its delegation: ns21.domaincontrol.com and ns22.domaincontrol.com.
The name server configuration of telements.com is shared with other domains, for instance juice-plus.biz, riceornice.com, camboxing.com and two others.
The two host names ns21.domaincontrol.com and ns22.domaincontrol.com each have a pair of IP addresses: ns21.domaincontrol.com has 97.74.100.11 and 2603:5:2141::b, and ns22.domaincontrol.com has 173.201.68.11 and 2603:5:2241::b.
Mail Servers
Mail for telements.com is handled by five mail servers, namely 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 telements.com are shared with other domains: wecity.io, aparentivf.com, onlydust.com and two others among them.
These mail servers are often deployed together with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 other mail servers.
Host names pointing to two IP addresses:
aspmx.l.google.com directs traffic to 64.233.180.27 and 2607:f8b0:4004:c23::1a.
alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com directs traffic to 192.178.223.27 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com directs traffic to 172.253.157.26 and 2a00:1450:400c:c23::1b.