dbfeed.com - robtex.com
dbfeed.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@dbfeed.com 2025-06-11 #2 | ||||||
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=1774702487 | ||||||
Previously MX for
dbfeed.com |
Same first word
dbfeed.com |
Similar names
DNS History
16 records (3 active, 13 former)
●NSns1.atom.com2026-03-05 → 2026-03-28 · 3 obs
○ 2019-04-09 21:48:34
● 2026-03-05 05:49:18
● 2026-03-28 13:11:56
● 2026-03-05 05:49:18
● 2026-03-28 13:11:56
○NSns1.dnslink.com2016-02-12 → 2017-01-30 · 6 obs
○ 2015-11-09 08:22:34
● 2016-02-12 08:20:46
○ 2016-06-22 18:14:58
● 2017-01-30 15:35:30
○ 2019-04-09 21:48:34
○ 2026-03-28 13:11:56
● 2016-02-12 08:20:46
○ 2016-06-22 18:14:58
● 2017-01-30 15:35:30
○ 2019-04-09 21:48:34
○ 2026-03-28 13:11:56
○NSns1.namebrightdns.com2019-04-09 → 2019-04-09 · 4 obs
○ 2017-01-30 15:35:30
● 2019-04-09 21:48:34
○ 2026-03-05 05:49:18
○ 2026-03-28 13:11:56
● 2019-04-09 21:48:34
○ 2026-03-05 05:49:18
○ 2026-03-28 13:11:56
○NSns1.vnic.com2015-07-03 → 2016-06-22 · 6 obs
● 2015-07-03 02:27:52
● 2015-11-09 08:22:34
○ 2016-02-12 08:20:46
● 2016-06-22 18:14:58
○ 2017-01-30 15:35:30
○ 2026-03-28 13:11:56
● 2015-11-09 08:22:34
○ 2016-02-12 08:20:46
● 2016-06-22 18:14:58
○ 2017-01-30 15:35:30
○ 2026-03-28 13:11:56
●NSns2.atom.com2026-03-05 → 2026-03-28 · 3 obs
○ 2019-04-09 21:48:34
● 2026-03-05 05:49:18
● 2026-03-28 13:11:56
● 2026-03-05 05:49:18
● 2026-03-28 13:11:56
○NSns2.dnslink.com2016-02-12 → 2017-01-30 · 6 obs
○ 2015-11-09 08:22:34
● 2016-02-12 08:20:46
○ 2016-06-22 18:14:58
● 2017-01-30 15:35:30
○ 2019-04-09 21:48:34
○ 2026-03-28 13:11:56
● 2016-02-12 08:20:46
○ 2016-06-22 18:14:58
● 2017-01-30 15:35:30
○ 2019-04-09 21:48:34
○ 2026-03-28 13:11:56
○NSns2.namebrightdns.com2019-04-09 → 2019-04-09 · 4 obs
○ 2017-01-30 15:35:30
● 2019-04-09 21:48:34
○ 2026-03-05 05:49:18
○ 2026-03-28 13:11:56
● 2019-04-09 21:48:34
○ 2026-03-05 05:49:18
○ 2026-03-28 13:11:56
○NSns2.vnic.com2015-07-03 → 2016-06-22 · 6 obs
● 2015-07-03 02:27:52
● 2015-11-09 08:22:34
○ 2016-02-12 08:20:46
● 2016-06-22 18:14:58
○ 2017-01-30 15:35:30
○ 2026-03-28 13:11:56
● 2015-11-09 08:22:34
○ 2016-02-12 08:20:46
● 2016-06-22 18:14:58
○ 2017-01-30 15:35:30
○ 2026-03-28 13:11:56
○MXdbfeed.com2015-07-03 → 2016-06-22 · 6 obs
● 2015-07-03 02:27:52
● 2015-11-09 08:22:34
○ 2016-02-12 08:20:46
● 2016-06-22 18:14:58
○ 2017-01-30 15:35:30
○ 2026-03-28 13:11:56
● 2015-11-09 08:22:34
○ 2016-02-12 08:20:46
● 2016-06-22 18:14:58
○ 2017-01-30 15:35:30
○ 2026-03-28 13:11:56
○MXmail.b-io.co2016-02-12 → 2017-01-30 · 6 obs
○ 2015-11-09 08:22:34
● 2016-02-12 08:20:46
○ 2016-06-22 18:14:58
● 2017-01-30 15:35:30
○ 2019-04-09 21:48:34
○ 2026-03-28 13:11:56
● 2016-02-12 08:20:46
○ 2016-06-22 18:14:58
● 2017-01-30 15:35:30
○ 2019-04-09 21:48:34
○ 2026-03-28 13:11:56
○MXmail1.namebrightmail.com2019-04-09 → 2019-04-09 · 4 obs
○ 2017-01-30 15:35:30
● 2019-04-09 21:48:34
○ 2026-03-05 05:49:18
○ 2026-03-28 13:11:56
● 2019-04-09 21:48:34
○ 2026-03-05 05:49:18
○ 2026-03-28 13:11:56
○MXmail2.namebrightmail.com2019-04-09 → 2019-04-09 · 4 obs
○ 2017-01-30 15:35:30
● 2019-04-09 21:48:34
○ 2026-03-05 05:49:18
○ 2026-03-28 13:11:56
● 2019-04-09 21:48:34
○ 2026-03-05 05:49:18
○ 2026-03-28 13:11:56
○A162.209.11.42015-07-03 → 2016-06-22 · 6 obs
● 2015-07-03 02:27:52
● 2015-11-09 08:22:34
○ 2016-02-12 08:20:46
● 2016-06-22 18:14:58
○ 2017-01-30 15:35:30
○ 2026-03-28 13:11:56
● 2015-11-09 08:22:34
○ 2016-02-12 08:20:46
● 2016-06-22 18:14:58
○ 2017-01-30 15:35:30
○ 2026-03-28 13:11:56
○A209.15.13.1342016-02-12 → 2017-01-30 · 6 obs
○ 2015-11-09 08:22:34
● 2016-02-12 08:20:46
○ 2016-06-22 18:14:58
● 2017-01-30 15:35:30
○ 2019-04-09 21:48:34
○ 2026-03-28 13:11:56
● 2016-02-12 08:20:46
○ 2016-06-22 18:14:58
● 2017-01-30 15:35:30
○ 2019-04-09 21:48:34
○ 2026-03-28 13:11:56
●A52.20.84.622026-03-05 → 2026-03-28 · 3 obs
○ 2019-04-09 21:48:34
● 2026-03-05 05:49:18
● 2026-03-28 13:11:56
● 2026-03-05 05:49:18
● 2026-03-28 13:11:56
○CNAMEurlforward.namebright.com2019-04-09 → 2019-04-09 · 3 obs
● 2019-04-09 21:48:34
○ 2026-03-05 05:49:18
○ 2026-03-28 13:11:56
○ 2026-03-05 05:49:18
○ 2026-03-28 13:11:56
🔍 DNS Trace
Analysis
IP Addresses
dbfeed.com resolves to a single IP: 52.20.84.62.
Other host names, for instance zaku.com, armseo.com, guerrillafilmmaking.com, wifirapid.com and webicles.com share IP numbers with dbfeed.com.
Name Servers
dbfeed.com has two name servers: ns1.atom.com and ns2.atom.com.
dbfeed.com shares the same name server setup as other domains, for example hdo.ai, smarthomebridge.com, trigro.com, prevelia.com and supportpoll.com.
dbfeed.com at least partially shares name servers with other domains; for example nettechconsulting.com and cream.net; ekinco.com and camvisor.com.
These name servers are commonly used together with ns1.afternic.com and ns2.afternic.com.
Host names with a single IP:
ns1.atom.com points to 44.219.81.145
ns2.atom.com points to 50.19.240.86