monitoring.com - dns.ninja
monitoring.com
| DNSSEC | β οΈ Not signed | ||||||
| NS | ns1.aftermarket.com β οΈ Not in zone NS records | ||||||
| A | 2600:1f16:529:db01::53πΊπΈ Amazon2600:1f16:400::/38 AMAZON AWS | ||||||
| A | 3.141.121.8πΊπΈ Amazon3.136.0.0/13 EC2 CMH prefix | ||||||
| PTR | ns1.aftermarket.com | ||||||
| NS | ns2.aftermarket.com β οΈ Not in zone NS records | ||||||
| A | 2600:1f16:529:db00::53πΊπΈ Amazon2600:1f16:400::/38 AMAZON AWS | ||||||
| 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=1786357634 | ||||||
Same first word
Similar names
motionring.com |
toromining.com |
motionring.net |
omnitoring.com |
ginmonitor.net |
ringmotion.com |
ginmonitor.com |
mooringtin.com |
rootmining.com |
DNS History
15 records (2 active, 13 former)
βNSns0.dnsmadeeasy.com2017-04-07 β 2017-11-20 Β· 5 obs
β 2016-09-04 22:41:12
β 2017-04-07 10:20:28
β 2017-11-20 15:29:04
β 2026-02-20 19:29:48
β 2026-08-10 10:55:18
β 2017-04-07 10:20:28
β 2017-11-20 15:29:04
β 2026-02-20 19:29:48
β 2026-08-10 10:55:18
βNSns1.aftermarket.com2026-02-20 β 2026-08-10 Β· 3 obs
β 2017-11-20 15:29:04
β 2026-02-20 19:29:48
β 2026-08-10 10:55:18
β 2026-02-20 19:29:48
β 2026-08-10 10:55:18
βNSns1.bellcanadahosting.com2015-08-23 β 2016-09-04 Β· 4 obs
β 2015-08-23 22:24:40
β 2016-09-04 22:41:12
β 2017-04-07 10:20:28
β 2026-08-10 10:55:18
β 2016-09-04 22:41:12
β 2017-04-07 10:20:28
β 2026-08-10 10:55:18
βNSns1.dnsmadeeasy.com2017-04-07 β 2017-11-20 Β· 5 obs
β 2016-09-04 22:41:12
β 2017-04-07 10:20:28
β 2017-11-20 15:29:04
β 2026-02-20 19:29:48
β 2026-08-10 10:55:18
β 2017-04-07 10:20:28
β 2017-11-20 15:29:04
β 2026-02-20 19:29:48
β 2026-08-10 10:55:18
βNSns2.aftermarket.com2026-02-20 β 2026-08-10 Β· 3 obs
β 2017-11-20 15:29:04
β 2026-02-20 19:29:48
β 2026-08-10 10:55:18
β 2026-02-20 19:29:48
β 2026-08-10 10:55:18
βNSns2.bellcanadahosting.com2015-08-23 β 2016-09-04 Β· 4 obs
β 2015-08-23 22:24:40
β 2016-09-04 22:41:12
β 2017-04-07 10:20:28
β 2026-08-10 10:55:18
β 2016-09-04 22:41:12
β 2017-04-07 10:20:28
β 2026-08-10 10:55:18
βNSns2.dnsmadeeasy.com2017-04-07 β 2017-11-20 Β· 5 obs
β 2016-09-04 22:41:12
β 2017-04-07 10:20:28
β 2017-11-20 15:29:04
β 2026-02-20 19:29:48
β 2026-08-10 10:55:18
β 2017-04-07 10:20:28
β 2017-11-20 15:29:04
β 2026-02-20 19:29:48
β 2026-08-10 10:55:18
βNSns3.bellcanadahosting.com2015-08-23 β 2016-09-04 Β· 4 obs
β 2015-08-23 22:24:40
β 2016-09-04 22:41:12
β 2017-04-07 10:20:28
β 2026-08-10 10:55:18
β 2016-09-04 22:41:12
β 2017-04-07 10:20:28
β 2026-08-10 10:55:18
βNSns3.dnsmadeeasy.com2017-04-07 β 2017-11-20 Β· 5 obs
β 2016-09-04 22:41:12
β 2017-04-07 10:20:28
β 2017-11-20 15:29:04
β 2026-02-20 19:29:48
β 2026-08-10 10:55:18
β 2017-04-07 10:20:28
β 2017-11-20 15:29:04
β 2026-02-20 19:29:48
β 2026-08-10 10:55:18
βNSns4.dnsmadeeasy.com2017-04-07 β 2017-11-20 Β· 5 obs
β 2016-09-04 22:41:12
β 2017-04-07 10:20:28
β 2017-11-20 15:29:04
β 2026-02-20 19:29:48
β 2026-08-10 10:55:18
β 2017-04-07 10:20:28
β 2017-11-20 15:29:04
β 2026-02-20 19:29:48
β 2026-08-10 10:55:18
βMXmx1c9.bellcanadahosting.com2015-08-23 β 2016-09-04 Β· 4 obs
β 2015-08-23 22:24:40
β 2016-09-04 22:41:12
β 2017-04-07 10:20:28
β 2026-08-10 10:55:18
β 2016-09-04 22:41:12
β 2017-04-07 10:20:28
β 2026-08-10 10:55:18
βMXmx2c9.bellcanadahosting.com2015-08-23 β 2016-09-04 Β· 4 obs
β 2015-08-23 22:24:40
β 2016-09-04 22:41:12
β 2017-04-07 10:20:28
β 2026-08-10 10:55:18
β 2016-09-04 22:41:12
β 2017-04-07 10:20:28
β 2026-08-10 10:55:18
βMXmx3c9.bellcanadahosting.com2015-08-23 β 2016-09-04 Β· 4 obs
β 2015-08-23 22:24:40
β 2016-09-04 22:41:12
β 2017-04-07 10:20:28
β 2026-08-10 10:55:18
β 2016-09-04 22:41:12
β 2017-04-07 10:20:28
β 2026-08-10 10:55:18
βA3.33.224.1472026-02-20 β 2026-07-08 Β· 13 obs
β 2017-04-07 10:20:28
β 2026-02-20 19:29:48
β 2026-04-17 21:41:28
β 2026-04-22 07:17:30
β 2026-04-27 07:13:34
β 2026-05-17 04:15:30
β 2026-05-23 11:58:30
β 2026-06-05 19:40:26
β 2026-06-10 21:40:18
β 2026-06-25 01:59:14
β 2026-07-08 01:16:32
β 2026-07-23 16:51:22
β 2026-08-10 10:55:18
β 2026-02-20 19:29:48
β 2026-04-17 21:41:28
β 2026-04-22 07:17:30
β 2026-04-27 07:13:34
β 2026-05-17 04:15:30
β 2026-05-23 11:58:30
β 2026-06-05 19:40:26
β 2026-06-10 21:40:18
β 2026-06-25 01:59:14
β 2026-07-08 01:16:32
β 2026-07-23 16:51:22
β 2026-08-10 10:55:18
βA69.156.240.292015-08-23 β 2016-09-04 Β· 4 obs
β 2015-08-23 22:24:40
β 2016-09-04 22:41:12
β 2017-04-07 10:20:28
β 2026-08-10 10:55:18
β 2016-09-04 22:41:12
β 2017-04-07 10:20:28
β 2026-08-10 10:55:18
π DNS Trace
Analysis
Name Servers
The NS records for monitoring.com delegate to ns1.aftermarket.com and ns2.aftermarket.com.
The name server configuration of monitoring.com is shared with other domains, for instance domainleap.com, marseo.com, rikkaus.com and two others.
At least some of monitoring.com's name servers are shared with other domains, for example fusetech.co.uk, iwalk.co.uk, medicaltech.co.uk and two more.
These name servers tend to be deployed in combination with the name servers ns1.domain.io and ns2.domain.io.
ns1.aftermarket.com resolves to 3.141.121.8 and 2600:1f16:529:db01::53. Likewise, ns2.aftermarket.com resolves to 3.15.73.134 and 2600:1f16:529:db00::53 β two IP addresses apiece.