keycoconstruction.com - dns.ninja
keycoconstruction.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=1784973177 | ||||||
Same first word
keycoconstruction.com |
Similar names
DNS History
11 records (11 active, 0 former)
●NScp1.privatesystems.net2026-02-24 → 2026-07-25 · 2 obs
● 2026-07-25 09:59:34
●NScp2.privatesystems.net2026-02-24 → 2026-07-25 · 2 obs
● 2026-07-25 09:59:34
●NScp3.privatesystems.net2026-02-24 → 2026-07-25 · 2 obs
● 2026-07-25 09:59:34
●NScp4.privatesystems.net2026-02-24 → 2026-07-25 · 2 obs
● 2026-07-25 09:59:34
●MXalt1.aspmx.l.google.com2026-02-24 → 2026-07-25 · 2 obs
● 2026-07-25 09:59:34
●MXalt2.aspmx.l.google.com2026-02-24 → 2026-07-25 · 2 obs
● 2026-07-25 09:59:34
●MXalt3.aspmx.l.google.com2026-02-24 → 2026-07-25 · 2 obs
● 2026-07-25 09:59:34
●MXalt4.aspmx.l.google.com2026-02-24 → 2026-07-25 · 2 obs
● 2026-07-25 09:59:34
●MXaspmx.l.google.com2026-02-24 → 2026-07-25 · 2 obs
● 2026-07-25 09:59:34
●A108.160.157.32026-02-24 → 2026-07-25 · 5 obs
● 2026-04-29 18:34:52
○ 2026-05-01 17:38:08
● 2026-06-13 16:37:28
● 2026-07-25 09:59:34
●A2600:4c00:500:bc09::a52026-02-24 → 2026-07-25 · 2 obs
● 2026-07-25 09:59:34
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| keycoconstruction.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 keycoconstruction.com (unsigned zone)
⏱️ Timing
Total: 2406ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 108.160.157.3 |
| AAAA | 1 | 2600:4c00:500:bc09::a5 |
| NS | 4 | cp3.privatesystems.net, cp2.privatesystems.net... |
| MX | 5 | ALT2.ASPMX.L.GOOGLE.com (pri: 5), ASPMX.L.GOOGLE.com (pri: 1)... |
| SOA | 1 | cp1.privatesystems.net noc.privatesystem |
Analysis
IP Addresses
keycoconstruction.com resolves to the IP addresses 108.160.157.3 and 2600:4c00:500:bc09::a5
wrightwoodcalif.com, winecoolr.com, discoverygroup.com.tw and two other host names share IP numbers with keycoconstruction.com.
Name Servers
The authoritative name servers for keycoconstruction.com are cp1.privatesystems.net, cp2.privatesystems.net, cp3.privatesystems.net and cp4.privatesystems.net.
keycoconstruction.com shares at least some of its name servers with other domains, including nextgeninstitute.com, belize.com.bz, tcaatn.com and two others.
Each of cp1.privatesystems.net, cp2.privatesystems.net, cp3.privatesystems.net and cp4.privatesystems.net has two IP addresses: cp1.privatesystems.net resolves to 158.106.136.90 and 2600:4c00:80:11::1; cp2.privatesystems.net resolves to 108.160.157.7 and 2600:4c00:509:731::a; cp3.privatesystems.net resolves to 158.106.136.36 and 2600:4c00:80:9::1; cp4.privatesystems.net resolves to 158.106.136.90 and 2600:4c00:80:11::1, matching cp1.privatesystems.net.
cp1.privatesystems.net along with cp4.privatesystems.net each resolve to 2600:4c00:80:11::1 IP addresses.
cp1.privatesystems.net along with cp4.privatesystems.net each resolve to 158.106.136.90 IP addresses.
Mail Servers
keycoconstruction.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
keycoconstruction.com has at least partial mail server overlap with other domains such as ns500693.ns500699.ns500693.ns500734.ns500693.ns500693.ns500699.ns500588.ns500588.ns500588.ns500699.ns500632.ns500632.ns500632.ns500588.ns500578.ns500110.dtrkdll.com, ns500742.ns500742.ns500671.ns500731.ns500742.ns500705.ns500688.ns500671.ns500649.ns500688.ns500671.ns500649.lustychickser.com, ns500671.ns500671.ns500742.ns500742.ns500754.ns500742.ns500754.ns500731.ns500688.ns500705.ns500671.ns500704.ns500678.ns500671.ns500688.ns500671.ns500649.lustychickser.com and two more.
The mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com are commonly seen alongside these mail servers.
Hostnames that resolve to two IP addresses:
aspmx.l.google.com resolves to two addresses: 142.250.31.26 and 2607:f8b0:4004:c1d::1a.
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::1b.
alt3.aspmx.l.google.com resolves to two addresses: 142.251.127.27 and 2a00:1450:4001:c21::1a.
alt4.aspmx.l.google.com resolves to two addresses: 172.253.148.26 and 2a00:1450:4025:4401::1b.