instaday.com - dns.ninja
instaday.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 13.56.33.8🇺🇸 Amazon13.56.0.0/16 EC2 Region prefix | ||||||
| PTR | ec2-13-56-33-8.us-west-1.compute.amazonaws.com | ||||||
| NS | ns1.brandbucket.com ⭐ | ||||||
| A | 2600:1f1c:800:8b01:2ba3:bb61:44fb:b361🇺🇸 Amazon2600:1f1c:800::/38 AMAZON AWS | ||||||
| A | 54.241.53.41🇺🇸 Amazon54.241.0.0/17 EC2 SFO prefix | ||||||
| PTR | ec2-54-241-53-41.us-west-1.compute.amazonaws.com | ||||||
| NS | ns2.brandbucket.com | ||||||
| A | 2600:1f16:54:8701:4012:7e34:5c5f:95a8🇺🇸 Amazon2600:1f16::/38 AMAZON AWS | ||||||
| A | 18.221.52.246🇺🇸 Amazon18.220.0.0/14 EC2 CMH prefix | ||||||
| PTR | ec2-18-221-52-246.us-east-2.compute.amazonaws.com | ||||||
| TXT | afternic-verification-cvgUQU8SkLxsjXcPBSk2CM | ||||||
| TXT | v=spf1 -all | ||||||
| TXT | 27aab5373841b85aab94982ee19ab62f96481ed6 | ||||||
| SOA | ns1.brandbucket.commail@instaday.com 2024-03-05 #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=1785540057 | ||||||
Same first word
instaday.com |
Similar names
DNS History
25 records (3 active, 22 former)
●NSns1.brandbucket.com2026-03-10 → 2026-07-31 · 3 obs
○ 2018-10-14 19:49:34
● 2026-03-10 13:00:46
● 2026-07-31 23:33:24
● 2026-03-10 13:00:46
● 2026-07-31 23:33:24
○NSns1.brandroot.com2018-10-14 → 2018-10-14 · 4 obs
○ 2017-02-12 03:59:00
● 2018-10-14 19:49:34
○ 2026-03-10 13:00:46
○ 2026-07-31 23:33:24
● 2018-10-14 19:49:34
○ 2026-03-10 13:00:46
○ 2026-07-31 23:33:24
○NSns1.domainmonster.com2017-02-12 → 2017-02-12 · 4 obs
○ 2016-06-29 07:27:00
● 2017-02-12 03:59:00
○ 2018-10-14 19:49:34
○ 2026-07-31 23:33:24
● 2017-02-12 03:59:00
○ 2018-10-14 19:49:34
○ 2026-07-31 23:33:24
○NSns1.hebergement-securise.com2015-11-11 → 2015-12-08 · 5 obs
○ 2015-06-20 19:15:20
● 2015-11-11 11:08:48
● 2015-12-08 21:39:12
○ 2016-01-30 16:32:36
○ 2026-07-31 23:33:24
● 2015-11-11 11:08:48
● 2015-12-08 21:39:12
○ 2016-01-30 16:32:36
○ 2026-07-31 23:33:24
○NSns1fkl.name.com2016-01-30 → 2016-06-29 · 5 obs
○ 2015-12-08 21:39:12
● 2016-01-30 16:32:36
● 2016-06-29 07:27:00
○ 2017-02-12 03:59:00
○ 2026-07-31 23:33:24
● 2016-01-30 16:32:36
● 2016-06-29 07:27:00
○ 2017-02-12 03:59:00
○ 2026-07-31 23:33:24
●NSns2.brandbucket.com2026-03-10 → 2026-07-31 · 3 obs
○ 2018-10-14 19:49:34
● 2026-03-10 13:00:46
● 2026-07-31 23:33:24
● 2026-03-10 13:00:46
● 2026-07-31 23:33:24
○NSns2.brandroot.com2018-10-14 → 2018-10-14 · 4 obs
○ 2017-02-12 03:59:00
● 2018-10-14 19:49:34
○ 2026-03-10 13:00:46
○ 2026-07-31 23:33:24
● 2018-10-14 19:49:34
○ 2026-03-10 13:00:46
○ 2026-07-31 23:33:24
○NSns2.domainmonster.com2017-02-12 → 2017-02-12 · 4 obs
○ 2016-06-29 07:27:00
● 2017-02-12 03:59:00
○ 2018-10-14 19:49:34
○ 2026-07-31 23:33:24
● 2017-02-12 03:59:00
○ 2018-10-14 19:49:34
○ 2026-07-31 23:33:24
○NSns2.hebergement-securise.com2015-11-11 → 2015-12-08 · 5 obs
○ 2015-06-20 19:15:20
● 2015-11-11 11:08:48
● 2015-12-08 21:39:12
○ 2016-01-30 16:32:36
○ 2026-07-31 23:33:24
● 2015-11-11 11:08:48
● 2015-12-08 21:39:12
○ 2016-01-30 16:32:36
○ 2026-07-31 23:33:24
○NSns2fln.name.com2016-01-30 → 2016-06-29 · 5 obs
○ 2015-12-08 21:39:12
● 2016-01-30 16:32:36
● 2016-06-29 07:27:00
○ 2017-02-12 03:59:00
○ 2026-07-31 23:33:24
● 2016-01-30 16:32:36
● 2016-06-29 07:27:00
○ 2017-02-12 03:59:00
○ 2026-07-31 23:33:24
○NSns3.domainmonster.com2017-02-12 → 2017-02-12 · 4 obs
○ 2016-06-29 07:27:00
● 2017-02-12 03:59:00
○ 2018-10-14 19:49:34
○ 2026-07-31 23:33:24
● 2017-02-12 03:59:00
○ 2018-10-14 19:49:34
○ 2026-07-31 23:33:24
○NSns3npv.name.com2016-01-30 → 2016-06-29 · 5 obs
○ 2015-12-08 21:39:12
● 2016-01-30 16:32:36
● 2016-06-29 07:27:00
○ 2017-02-12 03:59:00
○ 2026-07-31 23:33:24
● 2016-01-30 16:32:36
● 2016-06-29 07:27:00
○ 2017-02-12 03:59:00
○ 2026-07-31 23:33:24
○NSns4fpy.name.com2016-01-30 → 2016-06-29 · 5 obs
○ 2015-12-08 21:39:12
● 2016-01-30 16:32:36
● 2016-06-29 07:27:00
○ 2017-02-12 03:59:00
○ 2026-07-31 23:33:24
● 2016-01-30 16:32:36
● 2016-06-29 07:27:00
○ 2017-02-12 03:59:00
○ 2026-07-31 23:33:24
○NSns65.domaincontrol.com2015-06-20 → 2015-06-20 · 3 obs
● 2015-06-20 19:15:20
○ 2015-11-11 11:08:48
○ 2026-07-31 23:33:24
○ 2015-11-11 11:08:48
○ 2026-07-31 23:33:24
○NSns66.domaincontrol.com2015-06-20 → 2015-06-20 · 3 obs
● 2015-06-20 19:15:20
○ 2015-11-11 11:08:48
○ 2026-07-31 23:33:24
○ 2015-11-11 11:08:48
○ 2026-07-31 23:33:24
○MXhebergement-securise.com2015-11-11 → 2015-12-08 · 5 obs
○ 2015-06-20 19:15:20
● 2015-11-11 11:08:48
● 2015-12-08 21:39:12
○ 2016-01-30 16:32:36
○ 2026-07-31 23:33:24
● 2015-11-11 11:08:48
● 2015-12-08 21:39:12
○ 2016-01-30 16:32:36
○ 2026-07-31 23:33:24
○MXmailstore1.secureserver.net2015-06-20 → 2015-06-20 · 3 obs
● 2015-06-20 19:15:20
○ 2015-11-11 11:08:48
○ 2026-07-31 23:33:24
○ 2015-11-11 11:08:48
○ 2026-07-31 23:33:24
○MXmx.emailconfig.com2017-02-12 → 2017-02-12 · 4 obs
○ 2016-01-30 16:32:36
● 2017-02-12 03:59:00
○ 2018-10-14 19:49:34
○ 2026-07-31 23:33:24
● 2017-02-12 03:59:00
○ 2018-10-14 19:49:34
○ 2026-07-31 23:33:24
○MXsmtp.secureserver.net2015-06-20 → 2015-06-20 · 3 obs
● 2015-06-20 19:15:20
○ 2015-11-11 11:08:48
○ 2026-07-31 23:33:24
○ 2015-11-11 11:08:48
○ 2026-07-31 23:33:24
○A109.68.33.182017-02-12 → 2017-02-12 · 4 obs
○ 2016-06-29 07:27:00
● 2017-02-12 03:59:00
○ 2018-10-14 19:49:34
○ 2026-07-31 23:33:24
● 2017-02-12 03:59:00
○ 2018-10-14 19:49:34
○ 2026-07-31 23:33:24
●A13.56.33.82026-03-10 → 2026-07-31 · 3 obs
○ 2018-10-14 19:49:34
● 2026-03-10 13:00:46
● 2026-07-31 23:33:24
● 2026-03-10 13:00:46
● 2026-07-31 23:33:24
○A173.249.40.92018-10-14 → 2018-10-14 · 4 obs
○ 2017-02-12 03:59:00
● 2018-10-14 19:49:34
○ 2026-03-10 13:00:46
○ 2026-07-31 23:33:24
● 2018-10-14 19:49:34
○ 2026-03-10 13:00:46
○ 2026-07-31 23:33:24
○A184.168.221.772015-06-20 → 2015-06-20 · 3 obs
● 2015-06-20 19:15:20
○ 2015-11-11 11:08:48
○ 2026-07-31 23:33:24
○ 2015-11-11 11:08:48
○ 2026-07-31 23:33:24
○A212.83.179.762015-11-11 → 2015-12-08 · 5 obs
○ 2015-06-20 19:15:20
● 2015-11-11 11:08:48
● 2015-12-08 21:39:12
○ 2016-01-30 16:32:36
○ 2026-07-31 23:33:24
● 2015-11-11 11:08:48
● 2015-12-08 21:39:12
○ 2016-01-30 16:32:36
○ 2026-07-31 23:33:24
○A75.126.104.2432016-01-30 → 2016-06-29 · 5 obs
○ 2015-12-08 21:39:12
● 2016-01-30 16:32:36
● 2016-06-29 07:27:00
○ 2017-02-12 03:59:00
○ 2026-07-31 23:33:24
● 2016-01-30 16:32:36
● 2016-06-29 07:27:00
○ 2017-02-12 03:59:00
○ 2026-07-31 23:33:24
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | f.gtld-servers.net, b.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net... | - |
| instaday.com | ns1.brandbucket.com, ns2.brandbucket.com | 2 records |
✅ Authoritative Response
Server:54.241.53.41
NS records: ns1.brandbucket.com, ns2.brandbucket.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for instaday.com (unsigned zone)
⏱️ Timing
Total: 324ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 13.56.33.8 |
| NS | 2 | ns2.brandbucket.com, ns1.brandbucket.com |
| TXT | 3 | 27aab5373841b85aab94982ee19ab62f96481ed6, afternic-verification-cvgUQU8SkLxsjXcPBS... |
| SOA | 1 | ns1.brandbucket.com mail.instaday.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.brandbucket.com, ns2.brandbucket.com)
Analysis
IP Addresses
instaday.com directs to one IP number, which is 13.56.33.8.
Among the host names that share IP numbers with instaday.com are soneve.com, electronicmodel.com, pointily.com and two others.
Name Servers
The NS records for instaday.com delegate to ns1.brandbucket.com and ns2.brandbucket.com.
instaday.com has the same name server delegation as a number of other domains, such as pillina.com, ablephase.com, gamingspots.com and two more.
instaday.com partially shares its name servers with domains like maisonrue.com and cozera.com.
ns1.brandbucket.com resolves to 54.241.53.41 and 2600:1f1c:800:8b01:2ba3:bb61:44fb:b361. Likewise, ns2.brandbucket.com resolves to 18.221.52.246 and 2600:1f16:54:8701:4012:7e34:5c5f:95a8 — two IP addresses apiece.