insufficientdata.com - robtex.com
insufficientdata.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@insufficientdata.com 2026-09-29 #1 | ||||||
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=1794428181 | ||||||
Previously MX for
insufficientdata.com |
Same first word
insufficientdata.click |
insufficientdata.dev |
insufficientdata.eu |
insufficientdata.com |
insufficientdata.ca |
Previous names
Next names
DNS History
17 records (3 active, 14 former)
βNSbuy.internettraffic.com2016-03-11 β 2016-07-12 Β· 5 obs
β 2015-11-20 06:08:08
β 2016-03-11 04:56:38
β 2016-07-12 03:24:48
β 2017-03-20 14:12:00
β 2026-11-11 20:52:18
β 2016-03-11 04:56:38
β 2016-07-12 03:24:48
β 2017-03-20 14:12:00
β 2026-11-11 20:52:18
βNSns1.atom.com2026-09-05 β 2026-11-11 Β· 3 obs
β 2019-12-24 10:46:18
β 2026-09-05 18:36:16
β 2026-11-11 20:52:18
β 2026-09-05 18:36:16
β 2026-11-11 20:52:18
βNSns1.s013jp6654.info2015-07-07 β 2015-11-20 Β· 4 obs
β 2015-07-07 09:58:38
β 2015-11-20 06:08:08
β 2016-03-11 04:56:38
β 2026-11-11 20:52:18
β 2015-11-20 06:08:08
β 2016-03-11 04:56:38
β 2026-11-11 20:52:18
βNSns1.sedoparking.com2019-12-24 β 2019-12-24 Β· 4 obs
β 2017-03-20 14:12:00
β 2019-12-24 10:46:18
β 2026-09-05 18:36:16
β 2026-11-11 20:52:18
β 2019-12-24 10:46:18
β 2026-09-05 18:36:16
β 2026-11-11 20:52:18
βNSns1.uniregistrymarket.link2017-03-20 β 2017-03-20 Β· 4 obs
β 2016-07-12 03:24:48
β 2017-03-20 14:12:00
β 2019-12-24 10:46:18
β 2026-11-11 20:52:18
β 2017-03-20 14:12:00
β 2019-12-24 10:46:18
β 2026-11-11 20:52:18
βNSns2.atom.com2026-09-05 β 2026-11-11 Β· 3 obs
β 2019-12-24 10:46:18
β 2026-09-05 18:36:16
β 2026-11-11 20:52:18
β 2026-09-05 18:36:16
β 2026-11-11 20:52:18
βNSns2.s013jp6654.info2015-07-07 β 2015-11-20 Β· 4 obs
β 2015-07-07 09:58:38
β 2015-11-20 06:08:08
β 2016-03-11 04:56:38
β 2026-11-11 20:52:18
β 2015-11-20 06:08:08
β 2016-03-11 04:56:38
β 2026-11-11 20:52:18
βNSns2.sedoparking.com2019-12-24 β 2019-12-24 Β· 4 obs
β 2017-03-20 14:12:00
β 2019-12-24 10:46:18
β 2026-09-05 18:36:16
β 2026-11-11 20:52:18
β 2019-12-24 10:46:18
β 2026-09-05 18:36:16
β 2026-11-11 20:52:18
βNSns2.uniregistrymarket.link2017-03-20 β 2017-03-20 Β· 4 obs
β 2016-07-12 03:24:48
β 2017-03-20 14:12:00
β 2019-12-24 10:46:18
β 2026-11-11 20:52:18
β 2017-03-20 14:12:00
β 2019-12-24 10:46:18
β 2026-11-11 20:52:18
βNSsell.internettraffic.com2016-03-11 β 2016-07-12 Β· 5 obs
β 2015-11-20 06:08:08
β 2016-03-11 04:56:38
β 2016-07-12 03:24:48
β 2017-03-20 14:12:00
β 2026-11-11 20:52:18
β 2016-03-11 04:56:38
β 2016-07-12 03:24:48
β 2017-03-20 14:12:00
β 2026-11-11 20:52:18
βMXinsufficientdata.com2015-07-07 β 2015-11-20 Β· 4 obs
β 2015-07-07 09:58:38
β 2015-11-20 06:08:08
β 2016-03-11 04:56:38
β 2026-11-11 20:52:18
β 2015-11-20 06:08:08
β 2016-03-11 04:56:38
β 2026-11-11 20:52:18
βMXlocalhost2019-12-24 β 2019-12-24 Β· 4 obs
β 2016-03-11 04:56:38
β 2019-12-24 10:46:18
β 2026-09-05 18:36:16
β 2026-11-11 20:52:18
β 2019-12-24 10:46:18
β 2026-09-05 18:36:16
β 2026-11-11 20:52:18
βA210.224.188.2242015-07-07 β 2015-11-20 Β· 4 obs
β 2015-07-07 09:58:38
β 2015-11-20 06:08:08
β 2016-03-11 04:56:38
β 2026-11-11 20:52:18
β 2015-11-20 06:08:08
β 2016-03-11 04:56:38
β 2026-11-11 20:52:18
βA52.20.84.622026-09-05 β 2026-11-11 Β· 3 obs
β 2019-12-24 10:46:18
β 2026-09-05 18:36:16
β 2026-11-11 20:52:18
β 2026-09-05 18:36:16
β 2026-11-11 20:52:18
βA69.172.201.1532016-07-12 β 2017-03-20 Β· 5 obs
β 2016-03-11 04:56:38
β 2016-07-12 03:24:48
β 2017-03-20 14:12:00
β 2019-12-24 10:46:18
β 2026-11-11 20:52:18
β 2016-07-12 03:24:48
β 2017-03-20 14:12:00
β 2019-12-24 10:46:18
β 2026-11-11 20:52:18
βA69.172.201.2082016-03-11 β 2016-03-11 Β· 4 obs
β 2015-11-20 06:08:08
β 2016-03-11 04:56:38
β 2016-07-12 03:24:48
β 2026-11-11 20:52:18
β 2016-03-11 04:56:38
β 2016-07-12 03:24:48
β 2026-11-11 20:52:18
βA91.195.240.1262019-12-24 β 2019-12-24 Β· 4 obs
β 2017-03-20 14:12:00
β 2019-12-24 10:46:18
β 2026-09-05 18:36:16
β 2026-11-11 20:52:18
β 2019-12-24 10:46:18
β 2026-09-05 18:36:16
β 2026-11-11 20:52:18
π DNS Trace
Analysis
IP Addresses
insufficientdata.com resolves to just one IP address, 52.20.84.62.
Two other host names, along with assistpulse.com, region.tm and uniongrant.com, also share IP numbers with insufficientdata.com.
Name Servers
insufficientdata.com is served by two delegated name servers, ns1.atom.com and ns2.atom.com.
insufficientdata.com shares its NS records with other domains, for example allweldedlockers.com, sublimize.com, soloroam.com and two others.
insufficientdata.com and other domains like nolono.com, soranews.com and aikilibre.com share some name servers
Each of ns1.atom.com and ns2.atom.com has one IP address: ns1.atom.com uses 44.219.81.145 and ns2.atom.com uses 50.19.240.86.