protecttech.com - dns.ninja
protecttech.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 52.20.84.62🇺🇸 Amazon52.20.0.0/14 EC2 IAD prefix | ||||||
| PTR | ec2-52-20-84-62.compute-1.amazonaws.com | ||||||
| NS | ns1.atom.com ⭐ | ||||||
| A | 44.219.81.145🇺🇸 Amazon44.192.0.0/11 EC2 IAD prefix | ||||||
| PTR | ec2-44-219-81-145.compute-1.amazonaws.com | ||||||
| NS | ns2.atom.com | ||||||
| A | 50.19.240.86🇺🇸 Amazon50.19.128.0/17 EC2 IAD prefix | ||||||
| PTR | ec2-50-19-240-86.compute-1.amazonaws.com | ||||||
| SOA | ns1.atom.comhostmaster@protecttech.com 2025-02-04 #4 | ||||||
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=1782726675 | ||||||
Same first word
protecttech.ru |
protecttech.com |
Similar names
petrotechct.com |
techprotect.com |
techprotect.info |
techprotect.eu |
techprotect.us |
techprotect.org |
techprotect.de |
DNS History
24 records (3 active, 21 former)
○NSns1.namebrightdns.com2015-07-05 → 2017-01-21 · 8 obs
● 2015-07-05 20:32:44
○ 2015-11-19 21:26:38
○ 2016-02-08 02:09:48
● 2016-04-29 09:38:54
● 2017-01-21 12:38:40
○ 2020-04-10 03:49:58
○ 2026-06-29 10:18:06
○NSns2.namebrightdns.com2015-07-05 → 2017-01-21 · 7 obs
● 2015-07-05 20:32:44
○ 2015-11-19 21:26:38
○ 2016-04-29 09:38:54
● 2017-01-21 12:38:40
○ 2020-04-10 03:49:58
○ 2026-06-29 10:18:06
○NSns57.1and1.com2008-03-18 → 2008-03-18 · 3 obs
○ 2015-07-05 20:32:44
○ 2026-06-29 10:18:06
○NSns58.1and1.com2008-03-18 → 2008-03-18 · 3 obs
○ 2015-07-05 20:32:44
○ 2026-06-29 10:18:06
○NSnsg1.namebrightdns.com2015-11-19 → 2020-04-10 · 6 obs
● 2015-11-19 21:26:38
● 2016-04-29 09:38:54
○ 2017-01-21 12:38:40
● 2020-04-10 03:49:58
○ 2026-06-29 10:18:06
○NSnsg2.namebrightdns.com2015-11-19 → 2020-04-10 · 6 obs
● 2015-11-19 21:26:38
● 2016-04-29 09:38:54
○ 2017-01-21 12:38:40
● 2020-04-10 03:49:58
○ 2026-06-29 10:18:06
○MXanmail.namebrightmail.com2015-07-05 → 2015-07-05 · 4 obs
● 2015-07-05 20:32:44
○ 2015-11-19 21:26:38
○ 2026-06-29 10:18:06
○MXmx00.1and1.com2008-03-18 → 2008-03-18 · 3 obs
○ 2015-07-05 20:32:44
○ 2026-06-29 10:18:06
○MXmx01.1and1.com2008-03-18 → 2008-03-18 · 3 obs
○ 2015-07-05 20:32:44
○ 2026-06-29 10:18:06
○A52.0.96.242016-02-08 → 2016-02-08 · 4 obs
● 2016-02-08 02:09:48
○ 2016-04-29 09:38:54
○ 2026-06-29 10:18:06
●A52.20.84.622026-06-29 → 2026-06-29 · 2 obs
● 2026-06-29 10:18:06
○A52.200.243.1232016-04-29 → 2016-04-29 · 4 obs
● 2016-04-29 09:38:54
○ 2017-01-21 12:38:40
○ 2026-06-29 10:18:06
○A52.54.132.832017-01-21 → 2017-01-21 · 4 obs
● 2017-01-21 12:38:40
○ 2020-04-10 03:49:58
○ 2026-06-29 10:18:06
○A52.71.117.992016-02-08 → 2016-02-08 · 4 obs
● 2016-02-08 02:09:48
○ 2016-04-29 09:38:54
○ 2026-06-29 10:18:06
○A54.152.144.2432016-04-29 → 2016-04-29 · 4 obs
● 2016-04-29 09:38:54
○ 2017-01-21 12:38:40
○ 2026-06-29 10:18:06
○A54.174.31.2542015-07-05 → 2015-11-19 · 5 obs
● 2015-07-05 20:32:44
● 2015-11-19 21:26:38
○ 2016-02-08 02:09:48
○ 2026-06-29 10:18:06
○A54.208.74.2152015-07-05 → 2015-11-19 · 5 obs
● 2015-07-05 20:32:44
● 2015-11-19 21:26:38
○ 2016-02-08 02:09:48
○ 2026-06-29 10:18:06
○A54.88.107.1402017-01-21 → 2017-01-21 · 4 obs
● 2017-01-21 12:38:40
○ 2020-04-10 03:49:58
○ 2026-06-29 10:18:06
○A74.208.83.1692008-03-18 → 2008-03-18 · 3 obs
○ 2015-07-05 20:32:44
○ 2026-06-29 10:18:06
○CNAMEhdredirect-lb-399551664.us-east-1.elb.amazonaws.com2015-07-05 → 2016-04-29 · 5 obs
● 2015-07-05 20:32:44
● 2016-04-29 09:38:54
○ 2017-01-21 12:38:40
○ 2026-06-29 10:18:06
○CNAMEhdredirect-lb3-890977680.us-east-1.elb.amazonaws.com2017-01-21 → 2017-01-21 · 4 obs
● 2017-01-21 12:38:40
○ 2020-04-10 03:49:58
○ 2026-06-29 10:18:06
○CNAMEhdredirect-lb5-1afb6e2973825a56.elb.us-east-1.amazonaws.com2020-04-10 → 2020-04-10 · 3 obs
● 2020-04-10 03:49:58
○ 2026-06-29 10:18:06
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| protecttech.com | ns1.atom.com, ns2.atom.com | 2 records |
✅ Authoritative Response
Server:44.219.81.145
NS records: ns1.atom.com, ns2.atom.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for protecttech.com (unsigned zone)
⏱️ Timing
Total: 3068ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 52.20.84.62 |
| NS | 2 | ns1.atom.com, ns2.atom.com |
| SOA | 1 | ns1.atom.com hostmaster.protecttech.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.atom.com, ns2.atom.com)
Analysis
IP Addresses
protecttech.com has exactly one IP address — 52.20.84.62.
arcmatrix.com, autoox.com, schedlr.com plus two other host names have IP numbers in common with protecttech.com.
Name Servers
The NS records for protecttech.com delegate to ns1.atom.com and ns2.atom.com.
The name server configuration of protecttech.com is shared with other domains, for instance manslim.com, waypanel.com, visionpacific.com and two others.
protecttech.com and other domains like kartun.com share at least a portion of their name servers.
ns1.atom.com and ns2.atom.com each resolve to one IP number: ns1.atom.com points to 44.219.81.145 and ns2.atom.com points to 50.19.240.86.