protectsystems.com - dns.ninja
protectsystems.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=1785289897 | ||||||
Subdomains
www.protectsystems.com |
Same first word
protectsystems.com |
protectsystems.ru |
Similar names
DNS History
10 records (8 active, 2 former)
●NSpdns03.domaincontrol.com2026-03-13 → 2026-07-29 · 2 obs
● 2026-07-29 02:19:32
●NSpdns04.domaincontrol.com2026-03-13 → 2026-07-29 · 2 obs
● 2026-07-29 02:19:32
●MXalt1.aspmx.l.google.com2026-03-13 → 2026-07-29 · 2 obs
● 2026-07-29 02:19:32
●MXalt2.aspmx.l.google.com2026-03-13 → 2026-07-29 · 2 obs
● 2026-07-29 02:19:32
●MXalt3.aspmx.l.google.com2026-03-13 → 2026-07-29 · 2 obs
● 2026-07-29 02:19:32
●MXalt4.aspmx.l.google.com2026-03-13 → 2026-07-29 · 2 obs
● 2026-07-29 02:19:32
●MXaspmx.l.google.com2026-03-13 → 2026-07-29 · 2 obs
● 2026-07-29 02:19:32
●A192.124.249.1582026-03-13 → 2026-07-29 · 3 obs
● 2026-03-13 19:58:52
● 2026-07-29 02:19:32
○A207.148.248.1432015-10-26 → 2017-08-17 · 5 obs
● 2015-10-26 23:22:44
● 2017-08-17 00:33:28
○ 2026-03-13 19:58:52
○ 2026-07-29 02:19:32
○A66.151.181.492015-05-30 → 2015-05-30 · 3 obs
○ 2015-10-26 23:22:44
○ 2026-07-29 02:19:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | g.gtld-servers.net, m.gtld-servers.net, i.gtld-servers.net, a.gtld-servers.net... | - |
| protectsystems.com | pdns03.domaincontrol.com, pdns04.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.79.51
NS records: pdns03.domaincontrol.com, pdns04.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for protectsystems.com (unsigned zone)
⏱️ Timing
Total: 271ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 192.124.249.158 |
| NS | 2 | pdns03.domaincontrol.com, pdns04.domaincontrol.com |
| MX | 5 | alt2.aspmx.l.google.com (pri: 5), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 5 | v=spf1 include:_u.protectsystems.com._sp, google-site-verification=1vx9qQbGYl7tdlK... |
| SOA | 1 | pdns03.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (pdns03.domaincontrol.com, pdns03.domaincontrol.com, pdns04.domaincontrol.com...)
Analysis
Hierarchy
The domain www.protectsystems.com falls under the parent protectsystems.com.
IP Addresses
protectsystems.com resolves to just one IP address, 192.124.249.158.
Two other host names, along with ikti.org, tsfineart.com and garbryridge.com, also share IP numbers with protectsystems.com.
Name Servers
Two name servers handle the delegation for protectsystems.com: pdns03.domaincontrol.com and pdns04.domaincontrol.com.
protectsystems.com shares its NS records with other domains, for example nebulaterrible.com, cfcommunity.org, survivorbagproject.org and two others.
At least some of protectsystems.com's name servers are shared with other domains, for example secretinsociety.com and zafer.com.tr.
pdns03.domaincontrol.com and pdns04.domaincontrol.com both carry two IP addresses. The A records for pdns03.domaincontrol.com are 97.74.111.51 and 2603:5:21f0::33; the A records for pdns04.domaincontrol.com are 173.201.79.51 and 2603:5:22f0::33.
Mail Servers
Five mail servers handle protectsystems.com: 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 protectsystems.com and other domains, including ns500841.ns500841.ns500821.ns500794.ns500821.ns500794.ns500821.ns500821.ns500795.lustypartnersfinder.com, mayeswarddobbins.com, ns500731.ns500731.ns500731.ns500754.ns500704.ns500742.ns500705.ns500649.ns500649.ns500649.ns500649.ns500666.ns500142.lusty(0x736c7574)z.com and two others.
These mail servers tend to appear in combination with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.
Host names that have two IP addresses:
aspmx.l.google.com resolves to two addresses: 142.251.111.27 and 2607:f8b0:4004:c29::1a.
alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.27 and 2800:3f0:4003:c0f::1b.
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: 192.178.223.27 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com resolves to two addresses: 172.253.157.27 and 2a00:1450:400c:c23::1b.