templeslc.com - dns.ninja
templeslc.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | cp1.privatesystems.net ⚠️ Not in zone NS records | ||||||
| A | 2600:4c00:80:11::1🇺🇸 PRIVATESYSTEMS2600:4c00:80::/41 | ||||||
| A | 158.106.136.90🇺🇸 PRIVATESYSTEMS158.106.136.0/21 PrivateSystems Networks TX | ||||||
| PTR | cp1.privatesystems.net | ||||||
| NS | cp2.privatesystems.net ⚠️ Not in zone NS records | ||||||
| A | 2600:4c00:509:731::a🇺🇸 PRIVATESYSTEMS2600:4c00:500::/40 IPv6 subnet at SEF003 | ||||||
| A | 108.160.157.7🇺🇸 PRIVATESYSTEMS108.160.156.0/22 PrivateSystems Networks WA | ||||||
| NS | cp3.privatesystems.net ⚠️ Not in zone NS records | ||||||
| A | 2600:4c00:80:9::1🇺🇸 PRIVATESYSTEMS2600:4c00:80::/41 | ||||||
| A | 158.106.136.36🇺🇸 PRIVATESYSTEMS158.106.136.0/21 PrivateSystems Networks TX | ||||||
| NS | cp4.privatesystems.net ⚠️ Not in zone NS records | ||||||
| A | 2600:4c00:80:11::1🇺🇸 PRIVATESYSTEMS2600:4c00:80::/41 | ||||||
| A | 158.106.136.90🇺🇸 PRIVATESYSTEMS158.106.136.0/21 PrivateSystems Networks TX | ||||||
| PTR | cp1.privatesystems.net | ||||||
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=1786122269 | ||||||
Same first word
templeslc.com |
DNS History
5 records (4 active, 1 former)
●NScp1.privatesystems.net2026-02-22 → 2026-08-07 · 2 obs
● 2026-08-07 17:25:08
●NScp2.privatesystems.net2026-02-22 → 2026-08-07 · 2 obs
● 2026-08-07 17:25:08
●NScp3.privatesystems.net2026-02-22 → 2026-08-07 · 2 obs
● 2026-08-07 17:25:08
●NScp4.privatesystems.net2026-02-22 → 2026-08-07 · 2 obs
● 2026-08-07 17:25:08
○A50.87.144.1862015-07-02 → 2017-12-13 · 4 obs
● 2017-12-13 21:58:26
○ 2026-02-22 20:44:34
○ 2026-08-07 17:25:08
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | i.gtld-servers.net, k.gtld-servers.net, a.gtld-servers.net, e.gtld-servers.net... | - |
| templeslc.com | cp1.privatesystems.net, cp2.privatesystems.net, cp3.privatesystems.net, cp4.privatesystems.net | - |
✅ Authoritative Response
Server:158.106.136.90
NS records: cp1.privatesystems.net, cp2.privatesystems.net, cp3.privatesystems.net, cp4.privatesystems.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for templeslc.com (unsigned zone)
⏱️ Timing
Total: 377ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|
Analysis
Name Servers
The domain templeslc.com is delegated to these four name servers: cp1.privatesystems.net, cp2.privatesystems.net, cp3.privatesystems.net and cp4.privatesystems.net.
templeslc.com shares at least some of its name servers with other domains, including emdwebservices.com, apunto.mx, baykara.com and two others.
Two of the four hostnames share an address pair: cp1.privatesystems.net and cp4.privatesystems.net both resolve to 158.106.136.90 and 2600:4c00:80:11::1. The remaining hosts resolve to distinct addresses: cp2.privatesystems.net resolves to 108.160.157.7 and 2600:4c00:509:731::a, and cp3.privatesystems.net resolves to 158.106.136.36 and 2600:4c00:80:9::1.
Host names pointing to 2600:4c00:80:11::1 IP addresses: cp1.privatesystems.net and cp4.privatesystems.net.
Host names pointing to 158.106.136.90 IP addresses: cp1.privatesystems.net and cp4.privatesystems.net.