cryptoload.com - robtex.com
cryptoload.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.domain.io ⚠️ Not in zone NS records | ||||||
| A | 3.141.121.8🇺🇸 Amazon3.136.0.0/13 EC2 CMH prefix | ||||||
| PTR | ns1.aftermarket.com | ||||||
| NS | ns2.domain.io ⚠️ Not in zone NS records | ||||||
| A | 3.15.73.134🇺🇸 Amazon3.14.0.0/15 EC2 CMH prefix | ||||||
| PTR | ns2.aftermarket.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=1785103552 | ||||||
Previously NS for
cryptoload.com |
Same first word
cryptoload.com |
Similar names
DNS History
19 records (2 active, 17 former)
○NScryptoload.com2016-03-26 → 2017-05-16 · 5 obs
○ 2015-12-21 12:26:36
● 2016-03-26 21:47:44
● 2017-05-16 02:21:42
○ 2026-04-29 01:40:08
○ 2026-07-26 22:07:42
● 2016-03-26 21:47:44
● 2017-05-16 02:21:42
○ 2026-04-29 01:40:08
○ 2026-07-26 22:07:42
○NSis1.domainingdepot.com2016-03-26 → 2016-03-26 · 4 obs
○ 2015-12-21 12:26:36
● 2016-03-26 21:47:44
○ 2016-09-30 11:37:24
○ 2026-07-26 22:07:42
● 2016-03-26 21:47:44
○ 2016-09-30 11:37:24
○ 2026-07-26 22:07:42
○NSis2.domainingdepot.com2016-03-26 → 2016-03-26 · 4 obs
○ 2015-12-21 12:26:36
● 2016-03-26 21:47:44
○ 2016-09-30 11:37:24
○ 2026-07-26 22:07:42
● 2016-03-26 21:47:44
○ 2016-09-30 11:37:24
○ 2026-07-26 22:07:42
○NSns1.aftermarket.com2026-04-29 → 2026-04-29 · 4 obs
○ 2017-05-16 02:21:42
● 2026-04-29 01:40:08
○ 2026-04-29 15:37:40
○ 2026-07-26 22:07:42
● 2026-04-29 01:40:08
○ 2026-04-29 15:37:40
○ 2026-07-26 22:07:42
●NSns1.domain.io2026-04-29 → 2026-07-26 · 3 obs
○ 2017-05-16 02:21:42
● 2026-04-29 01:40:08
● 2026-07-26 22:07:42
● 2026-04-29 01:40:08
● 2026-07-26 22:07:42
○NSns1.dsredirection.com2015-08-12 → 2015-12-21 · 4 obs
● 2015-08-12 09:55:06
● 2015-12-21 12:26:36
○ 2016-03-26 21:47:44
○ 2026-07-26 22:07:42
● 2015-12-21 12:26:36
○ 2016-03-26 21:47:44
○ 2026-07-26 22:07:42
○NSns1.expiereddnsmanager.com2016-09-30 → 2017-05-16 · 5 obs
○ 2016-03-26 21:47:44
● 2016-09-30 11:37:24
● 2017-05-16 02:21:42
○ 2026-04-29 01:40:08
○ 2026-07-26 22:07:42
● 2016-09-30 11:37:24
● 2017-05-16 02:21:42
○ 2026-04-29 01:40:08
○ 2026-07-26 22:07:42
○NSns2.aftermarket.com2026-04-29 → 2026-04-29 · 4 obs
○ 2017-05-16 02:21:42
● 2026-04-29 01:40:08
○ 2026-04-29 15:37:40
○ 2026-07-26 22:07:42
● 2026-04-29 01:40:08
○ 2026-04-29 15:37:40
○ 2026-07-26 22:07:42
●NSns2.domain.io2026-04-29 → 2026-07-26 · 3 obs
○ 2017-05-16 02:21:42
● 2026-04-29 01:40:08
● 2026-07-26 22:07:42
● 2026-04-29 01:40:08
● 2026-07-26 22:07:42
○NSns2.dsredirection.com2015-08-12 → 2015-12-21 · 4 obs
● 2015-08-12 09:55:06
● 2015-12-21 12:26:36
○ 2016-03-26 21:47:44
○ 2026-07-26 22:07:42
● 2015-12-21 12:26:36
○ 2016-03-26 21:47:44
○ 2026-07-26 22:07:42
○NSns2.expiereddnsmanager.com2016-09-30 → 2017-05-16 · 5 obs
○ 2016-03-26 21:47:44
● 2016-09-30 11:37:24
● 2017-05-16 02:21:42
○ 2026-04-29 01:40:08
○ 2026-07-26 22:07:42
● 2016-09-30 11:37:24
● 2017-05-16 02:21:42
○ 2026-04-29 01:40:08
○ 2026-07-26 22:07:42
○MXmx7.cryptoload.com2016-03-26 → 2017-05-16 · 4 obs
● 2016-03-26 21:47:44
● 2017-05-16 02:21:42
○ 2026-04-29 01:40:08
○ 2026-07-26 22:07:42
● 2017-05-16 02:21:42
○ 2026-04-29 01:40:08
○ 2026-07-26 22:07:42
○A174.137.132.282016-03-26 → 2016-03-26 · 4 obs
○ 2015-12-21 12:26:36
● 2016-03-26 21:47:44
○ 2016-09-30 11:37:24
○ 2026-07-26 22:07:42
● 2016-03-26 21:47:44
○ 2016-09-30 11:37:24
○ 2026-07-26 22:07:42
○A208.73.210.2002015-08-12 → 2015-12-21 · 4 obs
● 2015-08-12 09:55:06
● 2015-12-21 12:26:36
○ 2016-03-26 21:47:44
○ 2026-07-26 22:07:42
● 2015-12-21 12:26:36
○ 2016-03-26 21:47:44
○ 2026-07-26 22:07:42
○A208.73.210.2142015-08-12 → 2015-12-21 · 4 obs
● 2015-08-12 09:55:06
● 2015-12-21 12:26:36
○ 2016-03-26 21:47:44
○ 2026-07-26 22:07:42
● 2015-12-21 12:26:36
○ 2016-03-26 21:47:44
○ 2026-07-26 22:07:42
○A208.73.210.2172015-08-12 → 2015-12-21 · 4 obs
● 2015-08-12 09:55:06
● 2015-12-21 12:26:36
○ 2016-03-26 21:47:44
○ 2026-07-26 22:07:42
● 2015-12-21 12:26:36
○ 2016-03-26 21:47:44
○ 2026-07-26 22:07:42
○A208.73.211.1782015-08-12 → 2015-12-21 · 4 obs
● 2015-08-12 09:55:06
● 2015-12-21 12:26:36
○ 2016-03-26 21:47:44
○ 2026-07-26 22:07:42
● 2015-12-21 12:26:36
○ 2016-03-26 21:47:44
○ 2026-07-26 22:07:42
○A213.247.47.1902016-09-30 → 2017-05-16 · 5 obs
○ 2016-03-26 21:47:44
● 2016-09-30 11:37:24
● 2017-05-16 02:21:42
○ 2026-04-29 01:40:08
○ 2026-07-26 22:07:42
● 2016-09-30 11:37:24
● 2017-05-16 02:21:42
○ 2026-04-29 01:40:08
○ 2026-07-26 22:07:42
○A3.33.224.1472026-04-29 → 2026-04-29 · 4 obs
○ 2017-05-16 02:21:42
● 2026-04-29 01:40:08
○ 2026-04-29 15:37:40
○ 2026-07-26 22:07:42
● 2026-04-29 01:40:08
○ 2026-04-29 15:37:40
○ 2026-07-26 22:07:42
🔍 DNS Trace
Analysis
Name Servers
Two name servers handle the delegation for cryptoload.com: ns1.domain.io and ns2.domain.io.
The name server configuration of cryptoload.com is shared with other domains, for instance atlasswiki.com, rumbleinthejungle.co.uk, cozmo.co.uk and two others.
The name servers of cryptoload.com overlap at least partially with those of other domains — among them leadproviders.com, rockbay.co.uk, pajobs.co.uk and two more.
These name servers commonly appear alongside the name servers ns1.aftermarket.com and ns2.aftermarket.com.
Both ns1.domain.io and ns2.domain.io have a single IP address each — ns1.domain.io resolves to 3.141.121.8 while ns2.domain.io resolves to 3.15.73.134.