`blazeadvisor.jp`

DNSSEC	⚠️ Not signed
A	3.33.139.32^{🇺🇸 Amazon3.33.128.0/20}
		PTR	`aeedc42b70c898c66.awsglobalaccelerator.com`
NS	`ha1.markmonitor.zone` ⭐ ⚠️ Not in parent delegation
		A	2001:67c:1bc::5^{🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD2001:67c:1bc::/48 IPCom-NET Anycast}
			PTR	`ha1.markmonitor.zone`
		A	192.174.68.5^{🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD192.174.68.0/24 NICat-anycast-net}
			PTR	`ha1.markmonitor.zone`
NS	`ha2.markmonitor.zone` ⚠️ Not in parent delegation
		A	2620:10a:80eb::6b^{🇨🇦 CIRA-22620:10a:80eb::/48 D-Zone Anycast Cloud 1}
			PTR	`ha2.markmonitor.zone`
		A	162.219.54.170^{🇨🇦 CIRA-2162.219.54.0/24 D-Zone Anycast Cloud1}
			PTR	`ha2.markmonitor.zone`
NS	`ha3.markmonitor.zone` ⚠️ Not in parent delegation
		A	2001:67c:10b8::5^{🇨🇭 RCODEZERO-ANYCAST-SEC22001:67c:10b8::/48 IPCOM-anycast-net}
			PTR	`ha3.markmonitor.zone`
		A	176.97.158.5^{🇦🇹 RCODEZERO-ANYCAST-SEC2176.97.158.0/24 NICat-anycast-net}
			PTR	`ha3.markmonitor.zone`
NS	`ha4.markmonitor.zone` ⚠️ Not in parent delegation
		A	2620:10a:80ec::6b^{🇨🇦 CIRA-32620:10a:80ec::/48 D-Zone IPv6 Anycast Cloud 2}
			PTR	`ha4.markmonitor.zone`
		A	162.219.55.170^{🇨🇦 CIRA-3162.219.55.0/24 D-Zone Anycast Cloud 2}
			PTR	`ha4.markmonitor.zone`
NS	`ns1.markmonitor.com` ⚠️ Not in zone NS records
		A	2620:10a:80a8::1^{🇨🇦 CIRA-22620:10a:80a8::/48 markmonitor v6 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.160.1^{🇨🇦 CIRA-2149.112.160.0/24 markmonitor v4 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
NS	`ns3.markmonitor.com` ⚠️ Not in zone NS records
		A	2620:10a:80a9::1^{🇨🇦 CIRA-32620:10a:80a9::/48 markmonitor v6 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.161.1^{🇨🇦 CIRA-3149.112.161.0/24 markmonitor v4 cloud2 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
NS	`ns4.markmonitor.com` ⚠️ Not in zone NS records
		A	2001:67c:1bc::1^{🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD2001:67c:1bc::/48 IPCom-NET Anycast}
			PTR	`ns1.markmonitor.com`
		A	192.174.68.1^{🇦🇹 RCODEZERO-ANYCAST-SEC1-TLD192.174.68.0/24 NICat-anycast-net}
			PTR	`ns1.markmonitor.com`
NS	`ns5.markmonitor.com` ⚠️ Not in zone NS records
		A	2620:10a:80a8::2^{🇨🇦 CIRA-22620:10a:80a8::/48 markmonitor v6 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
		A	149.112.160.2^{🇨🇦 CIRA-2149.112.160.0/24 markmonitor v4 cloud1 979 Bank Street, Suite 400 Ottawa ON K1S 5K5 Canada}
NS	`ns6.markmonitor.com` ⚠️ Not in zone NS records
		A	2001:67c:10b8::3^{🇨🇭 RCODEZERO-ANYCAST-SEC22001:67c:10b8::/48 IPCOM-anycast-net}
			PTR	`ns6.markmonitor.com`
		A	176.97.158.3^{🇦🇹 RCODEZERO-ANYCAST-SEC2176.97.158.0/24 NICat-anycast-net}
			PTR	`ns6.markmonitor.com`
MX	`noemail.invalid` ⭐
TXT	`v=spf1 -all`
SOA	`ha1.markmonitor.zone`hostmaster@markmonitor.com 2021-10-15 #2

`jp`

	DNSSEC	🔒 Signed (DS record present)
	NS	`z.dns.jp` ⭐
	NS	`a.dns.jp`
	NS	`b.dns.jp`
	NS	`c.dns.jp`
	NS	`d.dns.jp`
	NS	`e.dns.jp`
	NS	`f.dns.jp`
	NS	`g.dns.jp`
	NS	`h.dns.jp`
	SOA	`z.dns.jp`root@dns.jp serial=1778416203

Same first word

blazeadvisor.jp

blazeadvisor.com.ar

blazeadvisor.com.au

blazeadvisor.com.my

blazeadvisor.co.nz

blazeadvisor.be

blazeadvisor.co.at

blazeadvisor.sg

blazeadvisor.ch

blazeadvisor.se

blazeadvisor.at

blazeadvisor.ru

DNS History

14 records (11 active, 3 former)

●NSha1.markmonitor.zone2026-03-27 → 2026-05-10 · 3 obs

○ 2017-04-21 09:36:18
● 2026-03-27 03:52:18
● 2026-05-10 12:41:32

●NSha2.markmonitor.zone2026-03-27 → 2026-05-10 · 3 obs

○ 2017-04-21 09:36:18
● 2026-03-27 03:52:18
● 2026-05-10 12:41:32

●NSha3.markmonitor.zone2026-03-27 → 2026-05-10 · 3 obs

○ 2017-04-21 09:36:18
● 2026-03-27 03:52:18
● 2026-05-10 12:41:32

●NSha4.markmonitor.zone2026-03-27 → 2026-05-10 · 3 obs

○ 2017-04-21 09:36:18
● 2026-03-27 03:52:18
● 2026-05-10 12:41:32

●NSns1.markmonitor.com2015-08-17 → 2026-05-10 · 2 obs

● 2015-08-17 15:58:56
● 2026-05-10 12:41:32

○NSns2.markmonitor.com2015-08-17 → 2017-04-21 · 4 obs

● 2015-08-17 15:58:56
● 2017-04-21 09:36:18
○ 2026-03-27 03:52:18
○ 2026-05-10 12:41:32

●NSns3.markmonitor.com2015-08-17 → 2026-05-10 · 2 obs

● 2015-08-17 15:58:56
● 2026-05-10 12:41:32

●NSns4.markmonitor.com2015-08-17 → 2026-05-10 · 2 obs

● 2015-08-17 15:58:56
● 2026-05-10 12:41:32

●NSns5.markmonitor.com2015-08-17 → 2026-05-10 · 2 obs

● 2015-08-17 15:58:56
● 2026-05-10 12:41:32

●NSns6.markmonitor.com2015-08-17 → 2026-05-10 · 2 obs

● 2015-08-17 15:58:56
● 2026-05-10 12:41:32

○NSns7.markmonitor.com2015-08-17 → 2017-04-21 · 4 obs

● 2015-08-17 15:58:56
● 2017-04-21 09:36:18
○ 2026-03-27 03:52:18
○ 2026-05-10 12:41:32

●MXnoemail.invalid2026-03-27 → 2026-05-10 · 2 obs

● 2026-03-27 03:52:18
● 2026-05-10 12:41:32

●A3.33.139.322026-03-27 → 2026-05-10 · 3 obs

○ 2017-04-21 09:36:18
● 2026-03-27 03:52:18
● 2026-05-10 12:41:32

○A72.52.10.142015-08-17 → 2017-04-21 · 4 obs

● 2015-08-17 15:58:56
● 2017-04-21 09:36:18
○ 2026-03-27 03:52:18
○ 2026-05-10 12:41:32

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
jp	e.dns.jp, g.dns.jp, c.dns.jp, a.dns.jp...	-
blazeadvisor.jp	ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com, ns6.markmonitor.com...	-

✅ Authoritative Response

Server:176.97.158.3

NS records: ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com, ns6.markmonitor.com, ns1.markmonitor.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for blazeadvisor.jp (unsigned zone)

⏱️ Timing

Total: 1520ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`3.33.139.32`
NS	4	`ha3.markmonitor.zone, ha1.markmonitor.zone...`
MX	1	`noemail.invalid (pri: 0)`
TXT	1	`v=spf1 -all`
SOA	1	`ha1.markmonitor.zone hostmaster.markmoni`

Analysis

IP Addresses

blazeadvisor.jp resolves to one IP number: 3.33.139.32.

Other host names, for instance hiltonhawaiianvillage.cn, ns4.raid-vietnam.com, sperry.mx, shop4reebok.com and observatoire-tresorerie.org share IP numbers with blazeadvisor.jp.

Name Servers

blazeadvisor.jp is delegated to nine name servers: ns1.markmonitor.com, ns3.markmonitor.com, ns4.markmonitor.com, ns5.markmonitor.com, ns6.markmonitor.com, ha1.markmonitor.zone, ha2.markmonitor.zone, ha3.markmonitor.zone and ha4.markmonitor.zone.

blazeadvisor.jp at least partially shares name servers with other domains, including amazonlounge.com, perkinscoie.ru, museeatelieraudemarspiguet.org, paysafe.online and vurbotax.com.

These name servers are often used with ns2.markmonitor.com and ns7.markmonitor.com.

Host names with two IP numbers:

ns1.markmonitor.com points to: 2620:10a:80a8::1 and 149.112.160.1

ns3.markmonitor.com points to: 2620:10a:80a9::1 and 149.112.161.1

ns4.markmonitor.com points to: 2001:67c:1bc::1 and 192.174.68.1

ns5.markmonitor.com points to: 2620:10a:80a8::2 and 149.112.160.2

ns6.markmonitor.com points to: 2001:67c:10b8::3 and 176.97.158.3

ha1.markmonitor.zone points to: 2001:67c:1bc::5 and 192.174.68.5

ha2.markmonitor.zone points to: 2620:10a:80eb::6b and 162.219.54.170

ha3.markmonitor.zone points to: 2001:67c:10b8::5 and 176.97.158.5

ha4.markmonitor.zone points to: 2620:10a:80ec::6b and 162.219.55.170

Mail Servers

A single mail server handles blazeadvisor.jp, noemail.invalid.

blazeadvisor.jp shares the same mail server setup as other domains, for instance myfido.net, triad.cl, myficoscores.com, mail.coralis.it and www.ficoblog.com.

blazeadvisor.jp shares some mail servers with other domains, for instance mail.affinioninternational.dk, stanthonys.org, aachenlogo-live.gol.affinioninternational.de and affinioninternational.se.

These mail servers are often used together with the mail servers ..

blazeadvisor.jp - robtex.com

blazeadvisor.jp

jp

Same first word

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

Analysis

IP Addresses

Name Servers

Mail Servers

`blazeadvisor.jp`

`jp`