fancyaccess.com - dns.ninja

fancyaccess.com

DNSSEC⚠️ Not signed
A13.56.33.8🇺🇸 Amazon13.56.0.0/16 EC2 Region prefix
PTRec2-13-56-33-8.us-west-1.compute.amazonaws.com
NSns1.brandbucket.com
A2600:1f1c:800:8b01:2ba3:bb61:44fb:b361🇺🇸 Amazon2600:1f1c:800::/38 AMAZON AWS
A54.241.53.41🇺🇸 Amazon54.241.0.0/17 EC2 SFO prefix
PTRec2-54-241-53-41.us-west-1.compute.amazonaws.com
NSns2.brandbucket.com
A2600:1f16:54:8701:4012:7e34:5c5f:95a8🇺🇸 Amazon2600:1f16::/38 AMAZON AWS
A18.221.52.246🇺🇸 Amazon18.220.0.0/14 EC2 CMH prefix
PTRec2-18-221-52-246.us-east-2.compute.amazonaws.com
TXTv=spf1 -all
TXT27aab5373841b85aab94982ee19ab62f96481ed6
TXTafternic-verification-cvgUQU8SkLxsjXcPBSk2CM
SOAns1.brandbucket.commail@fancyaccess.com 2024-03-05 #2

com

Same first word

DNS History

3 records (3 active, 0 former)

202120222023202420252026NSns1.brandbucket.comns2.brandbucket.comA13.56.33.8
NSns1.brandbucket.com2020-02-20 → 2026-08-04 · 2 obs
● 2020-02-20 12:43:34
● 2026-08-04 07:31:10
NSns2.brandbucket.com2020-02-20 → 2026-08-04 · 2 obs
● 2020-02-20 12:43:34
● 2026-08-04 07:31:10
A13.56.33.82020-02-20 → 2026-08-04 · 2 obs
● 2020-02-20 12:43:34
● 2026-08-04 07:31:10

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
fancyaccess.comns1.brandbucket.com, ns2.brandbucket.com2 records

✅ Authoritative Response

Server:18.221.52.246

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for fancyaccess.com (unsigned zone)

⏱️ Timing

Total: 172ms | Queries: -

📄 Records

TypeCountSample Data
A113.56.33.8
NS2ns1.brandbucket.com, ns2.brandbucket.com
TXT327aab5373841b85aab94982ee19ab62f96481ed6, v=spf1 -all...
SOA1ns1.brandbucket.com mail.fancyaccess.com

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

fancyaccess.com has exactly one IP address — 13.56.33.8.

vorric.com, indism.com, meganomic.com plus two other host names have IP numbers in common with fancyaccess.com.

Name Servers

fancyaccess.com has two authoritative name servers — ns1.brandbucket.com and ns2.brandbucket.com.

The name server configuration of fancyaccess.com is shared with other domains, for instance telenion.com, asqa.com, olux.com and two others.

At least some of fancyaccess.com's name servers are shared with other domains, for example druph.com and silksister.com.

Both ns1.brandbucket.com and ns2.brandbucket.com have two IP addresses each. ns1.brandbucket.com resolves to 54.241.53.41 and 2600:1f1c:800:8b01:2ba3:bb61:44fb:b361; ns2.brandbucket.com resolves to 18.221.52.246 and 2600:1f16:54:8701:4012:7e34:5c5f:95a8.