fixpy.com - dns.ninja

fixpy.com

DNSSEC⚠️ Not signed
A54.166.76.105🇺🇸 Amazon54.166.0.0/15 EC2 IAD prefix
PTRec2-54-166-76-105.compute-1.amazonaws.com
NSns1.joshuadomains.com ⭐ ⚠️ Not in parent delegation
NSns1.brands.com ⚠️ Not in zone NS records
A54.166.76.105🇺🇸 Amazon54.166.0.0/15 EC2 IAD prefix
PTRec2-54-166-76-105.compute-1.amazonaws.com
NSns2.brands.com ⚠️ Not in zone NS records
A54.166.76.105🇺🇸 Amazon54.166.0.0/15 EC2 IAD prefix
PTRec2-54-166-76-105.compute-1.amazonaws.com
NSns2.joshuadomains.com ⚠️ Not in parent delegation
SOAns1.joshuadomains.comadmin@joshuadomains.com 2025-07-19 #1

com

Same first word

Similar names

DNS History

23 records (5 active, 18 former)

20162017201820192020202120222023202420252026NSns1.brands.comns1.joshuadomains.comns2.brands.comns2.joshuadomains.comdns1.registrar-servers.comdns2.registrar-servers.comeu.dnsenable.comhostmaster.dnsenable.comns1.dan.comns2.dan.comtr.dnsenable.comMXeforward1.registrar-servers.comeforward2.registrar-servers.comeforward3.registrar-servers.comeforward4.registrar-servers.comeforward5.registrar-servers.commail.fixpy.commx01.fixpy.comA54.166.76.105162.255.119.2492a05:d014:9da:8c10:306e:3e07:a16f:a55252.58.78.1693.89.226.17
NSdns1.registrar-servers.com2017-02-10 → 2017-02-10 · 4 obs
○ 2016-06-30 13:43:04
● 2017-02-10 03:44:58
○ 2020-03-14 09:36:02
○ 2026-07-28 01:23:52
NSdns2.registrar-servers.com2017-02-10 → 2017-02-10 · 4 obs
○ 2016-06-30 13:43:04
● 2017-02-10 03:44:58
○ 2020-03-14 09:36:02
○ 2026-07-28 01:23:52
NSeu.dnsenable.com2015-07-24 → 2016-06-30 · 4 obs
● 2015-07-24 03:38:08
● 2016-06-30 13:43:04
○ 2017-02-10 03:44:58
○ 2026-07-28 01:23:52
NShostmaster.dnsenable.com2015-07-24 → 2016-06-30 · 4 obs
● 2015-07-24 03:38:08
● 2016-06-30 13:43:04
○ 2017-02-10 03:44:58
○ 2026-07-28 01:23:52
NSns1.brands.com2026-02-18 → 2026-07-28 · 3 obs
○ 2020-03-14 09:36:02
● 2026-02-18 04:53:24
● 2026-07-28 01:23:52
NSns1.dan.com2020-03-14 → 2020-03-14 · 4 obs
○ 2017-02-10 03:44:58
● 2020-03-14 09:36:02
○ 2026-02-18 04:53:24
○ 2026-07-28 01:23:52
NSns1.joshuadomains.com2026-03-10 → 2026-07-28 · 3 obs
○ 2026-02-18 04:53:24
● 2026-03-10 18:09:58
● 2026-07-28 01:23:52
NSns2.brands.com2026-02-18 → 2026-07-28 · 3 obs
○ 2020-03-14 09:36:02
● 2026-02-18 04:53:24
● 2026-07-28 01:23:52
NSns2.dan.com2020-03-14 → 2020-03-14 · 4 obs
○ 2017-02-10 03:44:58
● 2020-03-14 09:36:02
○ 2026-02-18 04:53:24
○ 2026-07-28 01:23:52
NSns2.joshuadomains.com2026-03-10 → 2026-07-28 · 3 obs
○ 2026-02-18 04:53:24
● 2026-03-10 18:09:58
● 2026-07-28 01:23:52
NStr.dnsenable.com2015-07-24 → 2016-06-30 · 4 obs
● 2015-07-24 03:38:08
● 2016-06-30 13:43:04
○ 2017-02-10 03:44:58
○ 2026-07-28 01:23:52
MXeforward1.registrar-servers.com2017-02-10 → 2017-02-10 · 4 obs
○ 2016-06-30 13:43:04
● 2017-02-10 03:44:58
○ 2026-02-18 04:53:24
○ 2026-07-28 01:23:52
MXeforward2.registrar-servers.com2017-02-10 → 2017-02-10 · 4 obs
○ 2016-06-30 13:43:04
● 2017-02-10 03:44:58
○ 2026-02-18 04:53:24
○ 2026-07-28 01:23:52
MXeforward3.registrar-servers.com2017-02-10 → 2017-02-10 · 4 obs
○ 2016-06-30 13:43:04
● 2017-02-10 03:44:58
○ 2026-02-18 04:53:24
○ 2026-07-28 01:23:52
MXeforward4.registrar-servers.com2017-02-10 → 2017-02-10 · 4 obs
○ 2016-06-30 13:43:04
● 2017-02-10 03:44:58
○ 2026-02-18 04:53:24
○ 2026-07-28 01:23:52
MXeforward5.registrar-servers.com2017-02-10 → 2017-02-10 · 4 obs
○ 2016-06-30 13:43:04
● 2017-02-10 03:44:58
○ 2026-02-18 04:53:24
○ 2026-07-28 01:23:52
MXmail.fixpy.com2015-07-24 → 2016-06-30 · 4 obs
● 2015-07-24 03:38:08
● 2016-06-30 13:43:04
○ 2017-02-10 03:44:58
○ 2026-07-28 01:23:52
MXmx01.fixpy.com2015-07-24 → 2016-06-30 · 4 obs
● 2015-07-24 03:38:08
● 2016-06-30 13:43:04
○ 2017-02-10 03:44:58
○ 2026-07-28 01:23:52
A162.255.119.2492017-02-10 → 2017-02-10 · 4 obs
○ 2016-06-30 13:43:04
● 2017-02-10 03:44:58
○ 2020-03-14 09:36:02
○ 2026-07-28 01:23:52
A2a05:d014:9da:8c10:306e:3e07:a16f:a5522020-03-14 → 2020-03-14 · 4 obs
○ 2017-02-10 03:44:58
● 2020-03-14 09:36:02
○ 2026-02-18 04:53:24
○ 2026-07-28 01:23:52
A52.58.78.162020-03-14 → 2020-03-14 · 4 obs
○ 2017-02-10 03:44:58
● 2020-03-14 09:36:02
○ 2026-02-18 04:53:24
○ 2026-07-28 01:23:52
A54.166.76.1052026-02-18 → 2026-07-28 · 3 obs
○ 2020-03-14 09:36:02
● 2026-02-18 04:53:24
● 2026-07-28 01:23:52
A93.89.226.172015-07-24 → 2016-06-30 · 4 obs
● 2015-07-24 03:38:08
● 2016-06-30 13:43:04
○ 2017-02-10 03:44:58
○ 2026-07-28 01:23:52

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
comi.gtld-servers.net, k.gtld-servers.net, d.gtld-servers.net, a.gtld-servers.net...-
fixpy.comns1.brands.com, ns2.brands.com2 records

✅ Authoritative Response

Server:54.166.76.105

NS records: ns1.brands.com, ns2.brands.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for fixpy.com (unsigned zone)

⏱️ Timing

Total: 294ms | Queries: -

📄 Records

TypeCountSample Data
A154.166.76.105
NS2ns1.joshuadomains.com, ns2.joshuadomains.com
SOA1ns1.joshuadomains.com admin.joshuadomain

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.brands.com, ns2.brands.com)

Analysis

IP Addresses

fixpy.com points to a single IP number: 54.166.76.105.

Additional host names — icecreams.com, yimmi.com, oxhu.com and two others — share IP numbers with fixpy.com.

Name Servers

fixpy.com has four authoritative name servers: ns1.brands.com, ns2.brands.com, ns1.joshuadomains.com and ns2.joshuadomains.com.

fixpy.com partially shares its NS delegation with several other domains, including isbu.com, chewee.com, bezu.com and two others.

These name servers often co-occur with the name servers verification-amrhhgf2cgmsf6uxqt8ddn.ns101.verify.hn.

ns1.brands.com directs to 54.166.76.105, as does ns2.brands.com — both hostnames resolve to that one IP address.

ns1.brands.com along with ns2.brands.com each resolve to 54.166.76.105 IP addresses.