studiohuzzy.com - dns.ninja
studiohuzzy.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=1784868277 | ||||||
Same first word
studiohuzzy.com |
DNS History
10 records (8 active, 2 former)
●NSns1.netfirms.com2016-12-21 → 2026-07-24 · 2 obs
● 2026-07-24 04:51:24
●NSns2.netfirms.com2016-12-21 → 2026-07-24 · 2 obs
● 2026-07-24 04:51:24
●MXalt1.aspmx.l.google.com2019-01-21 → 2026-07-24 · 3 obs
● 2019-01-21 20:07:58
● 2026-07-24 04:51:24
●MXalt2.aspmx.l.google.com2019-01-21 → 2026-07-24 · 3 obs
● 2019-01-21 20:07:58
● 2026-07-24 04:51:24
●MXaspmx.l.google.com2019-01-21 → 2026-07-24 · 3 obs
● 2019-01-21 20:07:58
● 2026-07-24 04:51:24
●MXaspmx2.googlemail.com2019-01-21 → 2026-07-24 · 3 obs
● 2019-01-21 20:07:58
● 2026-07-24 04:51:24
●MXaspmx3.googlemail.com2019-01-21 → 2026-07-24 · 3 obs
● 2019-01-21 20:07:58
● 2026-07-24 04:51:24
○MXmx.studiohuzzy.com2016-12-21 → 2016-12-21 · 3 obs
○ 2019-01-21 20:07:58
○ 2026-07-24 04:51:24
●A144.217.248.1872019-01-21 → 2026-07-24 · 3 obs
● 2019-01-21 20:07:58
● 2026-07-24 04:51:24
○A69.42.58.1132016-12-21 → 2016-12-21 · 3 obs
○ 2019-01-21 20:07:58
○ 2026-07-24 04:51:24
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, l.gtld-servers.net, f.gtld-servers.net, c.gtld-servers.net... | - |
| studiohuzzy.com | ns1.netfirms.com, ns2.netfirms.com | 4 records |
✅ Authoritative Response
Server:162.159.24.252
NS records: ns1.netfirms.com, ns2.netfirms.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for studiohuzzy.com (unsigned zone)
⏱️ Timing
Total: 257ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 144.217.248.187 |
| NS | 2 | ns2.netfirms.com, ns1.netfirms.com |
| MX | 5 | ASPMX.L.GOOGLE.com (pri: 1), ASPMX3.GOOGLEMAIL.com (pri: 10)... |
| TXT | 1 | v=spf1 ip4:66.96.128.0/18 include:websit |
| SOA | 1 | ns1.netfirms.com hostmaster.netfirms.com |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns1.netfirms.com, ns1.netfirms.com, ns2.netfirms.com...)
Analysis
IP Addresses
studiohuzzy.com resolves to just one IP address, 144.217.248.187.
Two other host names, along with vikingsgatineau.ca, spcdc.ca and seedsystems.net, also share IP numbers with studiohuzzy.com.
Name Servers
studiohuzzy.com is served by two delegated name servers, ns1.netfirms.com and ns2.netfirms.com.
studiohuzzy.com shares its NS records with other domains, for example accessandparking.com, concentric.ca, cloudflow.ca and two others.
At least some of studiohuzzy.com's name servers are shared with other domains, for example theconnfamily.ca, propertyedge.ca, fxen.com and two more.
It is common for these name servers to be used in conjunction with the name servers ns1.yourhostingaccount.com, ns2.yourhostingaccount.com and ns1.dotster.com.
Each of ns1.netfirms.com and ns2.netfirms.com has one IP address: ns1.netfirms.com uses 162.159.24.252 and ns2.netfirms.com uses 162.159.25.208.
Mail Servers
studiohuzzy.com has five mail servers, which are aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
There is at least a partial MX overlap between studiohuzzy.com and other domains, including ns500731.ns500731.ns500742.ns500731.ns500754.ns500671.ns500688.ns500688.ns500678.ns500671.ns500671.ns500666.tenderladiesbz.com, ns500754.ns500671.ns500742.ns500731.ns500754.ns500754.ns500704.ns500704.ns500678.ns500705.ns500671.ns500649.ns500649.ns500666.ns500142.lusty(0x736c7574)z.com, ns500734.ns500699.ns500693.ns500693.ns500734.ns500728.ns500588.ns500588.ns500588.ns500683.ns500699.ns500693.ns500612.ns500588.ns500588.dtrkdll.com and two others.
These mail servers tend to appear in combination with mail servers alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.
Host names that have two IP addresses:
aspmx2.googlemail.com maps to two IP addresses — 108.177.123.27 and 2800:3f0:4003:c0f::1b.
aspmx3.googlemail.com maps to two IP addresses — 172.253.116.26 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com maps to two IP addresses — 192.178.155.26 and 2607:f8b0:4004:c1f::1a.
alt1.aspmx.l.google.com maps to two IP addresses — 108.177.123.27 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com maps to two IP addresses — 172.253.116.26 and 2a00:1450:400b:c02::1a.
These two host names — aspmx2.googlemail.com and alt1.aspmx.l.google.com — each point to 108.177.123.27 IP addresses.
These two host names — aspmx3.googlemail.com and alt2.aspmx.l.google.com — each point to 2a00:1450:400b:c02::1a IP addresses.
These two host names — aspmx3.googlemail.com and alt2.aspmx.l.google.com — each point to 172.253.116.26 IP addresses.