criptopay.com - robtex.com
criptopay.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.uniregistrymarket.link ⚠️ Not in zone NS records | ||||||
| A | 52.89.18.51🇺🇸 Amazon52.88.0.0/15 EC2 PDX Prefix | ||||||
| PTR | ec2-52-89-18-51.us-west-2.compute.amazonaws.com | ||||||
| A | 54.152.30.238🇺🇸 Amazon54.152.0.0/16 EC2 IAD prefix | ||||||
| PTR | ec2-54-152-30-238.compute-1.amazonaws.com | ||||||
| NS | ns2.uniregistrymarket.link ⚠️ Not in zone NS records | ||||||
| A | 18.217.16.210🇺🇸 Amazon18.216.0.0/14 EC2 CMH prefix | ||||||
| PTR | ec2-18-217-16-210.us-east-2.compute.amazonaws.com | ||||||
| A | 34.247.146.68🇮🇪 Amazon34.240.0.0/13 EC2 DUB prefix | ||||||
| PTR | ec2-34-247-146-68.eu-west-1.compute.amazonaws.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=1787910095 | ||||||
Same first word
criptopay.pages.dev |
criptopay.com |
Similar names
Previous names
Next names
DNS History
16 records (2 active, 14 former)
○NSdns1.registrar-servers.com2015-08-21 → 2017-02-12 · 6 obs
● 2015-08-21 17:14:30
● 2016-01-12 18:07:14
○ 2016-04-24 06:46:50
● 2017-02-12 20:08:26
○ 2026-08-19 16:13:42
○ 2026-08-28 10:02:46
● 2016-01-12 18:07:14
○ 2016-04-24 06:46:50
● 2017-02-12 20:08:26
○ 2026-08-19 16:13:42
○ 2026-08-28 10:02:46
○NSdns1.registrar-servers.com,2016-04-24 → 2016-04-24 · 4 obs
○ 2016-01-12 18:07:14
● 2016-04-24 06:46:50
○ 2017-02-12 20:08:26
○ 2026-08-28 10:02:46
● 2016-04-24 06:46:50
○ 2017-02-12 20:08:26
○ 2026-08-28 10:02:46
○NSdns2.registrar-servers.com2015-08-21 → 2017-02-12 · 4 obs
● 2015-08-21 17:14:30
● 2017-02-12 20:08:26
○ 2026-08-19 16:13:42
○ 2026-08-28 10:02:46
● 2017-02-12 20:08:26
○ 2026-08-19 16:13:42
○ 2026-08-28 10:02:46
○NSdns3.registrar-servers.com2015-08-21 → 2016-04-24 · 4 obs
● 2015-08-21 17:14:30
● 2016-04-24 06:46:50
○ 2017-02-12 20:08:26
○ 2026-08-28 10:02:46
● 2016-04-24 06:46:50
○ 2017-02-12 20:08:26
○ 2026-08-28 10:02:46
○NSdns4.registrar-servers.com2015-08-21 → 2016-04-24 · 4 obs
● 2015-08-21 17:14:30
● 2016-04-24 06:46:50
○ 2017-02-12 20:08:26
○ 2026-08-28 10:02:46
● 2016-04-24 06:46:50
○ 2017-02-12 20:08:26
○ 2026-08-28 10:02:46
○NSdns5.registrar-servers.com2015-08-21 → 2016-04-24 · 4 obs
● 2015-08-21 17:14:30
● 2016-04-24 06:46:50
○ 2017-02-12 20:08:26
○ 2026-08-28 10:02:46
● 2016-04-24 06:46:50
○ 2017-02-12 20:08:26
○ 2026-08-28 10:02:46
●NSns1.uniregistrymarket.link2026-08-19 → 2026-08-28 · 3 obs
○ 2017-02-12 20:08:26
● 2026-08-19 16:13:42
● 2026-08-28 10:02:46
● 2026-08-19 16:13:42
● 2026-08-28 10:02:46
●NSns2.uniregistrymarket.link2026-08-19 → 2026-08-28 · 3 obs
○ 2017-02-12 20:08:26
● 2026-08-19 16:13:42
● 2026-08-28 10:02:46
● 2026-08-19 16:13:42
● 2026-08-28 10:02:46
○MXeforward1.registrar-servers.com2015-08-21 → 2017-02-12 · 4 obs
● 2015-08-21 17:14:30
● 2017-02-12 20:08:26
○ 2026-08-19 16:13:42
○ 2026-08-28 10:02:46
● 2017-02-12 20:08:26
○ 2026-08-19 16:13:42
○ 2026-08-28 10:02:46
○MXeforward2.registrar-servers.com2015-08-21 → 2017-02-12 · 4 obs
● 2015-08-21 17:14:30
● 2017-02-12 20:08:26
○ 2026-08-19 16:13:42
○ 2026-08-28 10:02:46
● 2017-02-12 20:08:26
○ 2026-08-19 16:13:42
○ 2026-08-28 10:02:46
○MXeforward3.registrar-servers.com2015-08-21 → 2017-02-12 · 4 obs
● 2015-08-21 17:14:30
● 2017-02-12 20:08:26
○ 2026-08-19 16:13:42
○ 2026-08-28 10:02:46
● 2017-02-12 20:08:26
○ 2026-08-19 16:13:42
○ 2026-08-28 10:02:46
○MXeforward4.registrar-servers.com2015-08-21 → 2017-02-12 · 4 obs
● 2015-08-21 17:14:30
● 2017-02-12 20:08:26
○ 2026-08-19 16:13:42
○ 2026-08-28 10:02:46
● 2017-02-12 20:08:26
○ 2026-08-19 16:13:42
○ 2026-08-28 10:02:46
○MXeforward5.registrar-servers.com2015-08-21 → 2017-02-12 · 4 obs
● 2015-08-21 17:14:30
● 2017-02-12 20:08:26
○ 2026-08-19 16:13:42
○ 2026-08-28 10:02:46
● 2017-02-12 20:08:26
○ 2026-08-19 16:13:42
○ 2026-08-28 10:02:46
○A162.255.119.2512016-01-12 → 2016-01-12 · 4 obs
○ 2015-12-05 12:30:32
● 2016-01-12 18:07:14
○ 2016-04-24 06:46:50
○ 2026-08-28 10:02:46
● 2016-01-12 18:07:14
○ 2016-04-24 06:46:50
○ 2026-08-28 10:02:46
○A192.64.119.682016-04-24 → 2016-04-24 · 4 obs
○ 2016-01-12 18:07:14
● 2016-04-24 06:46:50
○ 2017-02-12 20:08:26
○ 2026-08-28 10:02:46
● 2016-04-24 06:46:50
○ 2017-02-12 20:08:26
○ 2026-08-28 10:02:46
○A192.64.119.772015-08-21 → 2015-12-05 · 4 obs
● 2015-08-21 17:14:30
● 2015-12-05 12:30:32
○ 2016-01-12 18:07:14
○ 2026-08-28 10:02:46
● 2015-12-05 12:30:32
○ 2016-01-12 18:07:14
○ 2026-08-28 10:02:46
🔍 DNS Trace
Analysis
Name Servers
criptopay.com has two authoritative name servers — ns1.uniregistrymarket.link and ns2.uniregistrymarket.link.
criptopay.com shares its NS records with other domains, for example uqw.in, superary.com, localready.com and two others.
At least some of criptopay.com's name servers are shared with other domains, for example oasos.com and androidwatch.com.
Both ns1.uniregistrymarket.link and ns2.uniregistrymarket.link have two IP addresses each. ns1.uniregistrymarket.link resolves to 52.89.18.51 and 54.152.30.238; ns2.uniregistrymarket.link resolves to 18.217.16.210 and 34.247.146.68.