`h2fc-tokyo.com`

DNSSEC	⚠️ Not signed
A	46.51.244.145^{🇯🇵 Amazon46.51.224.0/19 EC2 NRT prefix}
		PTR	`ec2-46-51-244-145.ap-northeast-1.compute.amazonaws.com`
NS	`h2fc-tokyo.com` ⭐
		A	46.51.244.145^{🇯🇵 Amazon46.51.224.0/19 EC2 NRT prefix}
			PTR	`ec2-46-51-244-145.ap-northeast-1.compute.amazonaws.com`
NS	`dns01.muumuu-domain.com`
		A	202.239.23.39^{🇯🇵 IDC202.239.23.0/24 Frontier Inc.}
NS	`dns02.muumuu-domain.com`
		A	160.251.249.62^{🇯🇵 GMOOSK-NET160.251.128.0/17 GMO Internet,Inc Cerulean Tower, 11F Sakuragaokacho-26-1 Shibuya-ku, Tokyo 150-8512, Japan}
MX	`aspmx.l.google.com` ⭐
		A	2a00:1450:4009:c19::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrp-in-f26.1e100.net`
		A	192.178.223.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽²⁰⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.26^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽²⁰⁾
		A	2607:f8b0:4023:1015::1b^{🇺🇸 Google2607:f8b0::/32}
			PTR	`yudfwta-in-f27.1e100.net`
		A	172.253.135.26^{🇺🇸 Google172.253.135.0/24}
			PTR	`yudfwta-in-f26.1e100.net`
MX	`aspmx2.googlemail.com`⁽³⁰⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.26^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f26.1e100.net`
MX	`aspmx3.googlemail.com`⁽³⁰⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`aspmx4.googlemail.com`⁽³⁰⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`aspmx5.googlemail.com`⁽³⁰⁾
		A	2a00:1450:400c:c00::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`ws-in-f26.1e100.net`
			PTR	`ws-in-x1a.1e100.net`
		A	173.194.76.27^{🇺🇸 Google173.194.76.0/24}
			PTR	`ws-in-f27.1e100.net`
TXT	`v=spf1 ip4:46.51.250.243 include:_spf.google.com ~all`
TXT	`google-site-verification=7oXzn7UpTBk8wYpYfQdrgAMh4E35EB_VyBdBLwQFYLE`
SOA	`h2fc-tokyo.com`postmaster@h2fc-tokyo.com serial=1711532528

`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.net`nstld@verisign-grs.com serial=1776168862

NS for

h2fc-tokyo.com

Subdomains

www.h2fc-tokyo.com

Same first word

h2fc-tokyo.com

DNS History

12 records (11 active, 1 former)

●NSdns01.muumuu-domain.com2015-06-18 → 2026-04-14 · 2 obs

● 2015-06-18 23:25:52
● 2026-04-14 12:24:58

●NSdns02.muumuu-domain.com2015-06-18 → 2026-04-14 · 2 obs

● 2015-06-18 23:25:52
● 2026-04-14 12:24:58

●NSh2fc-tokyo.com2015-06-18 → 2026-04-14 · 2 obs

● 2015-06-18 23:25:52
● 2026-04-14 12:24:58

●MXalt1.aspmx.l.google.com2015-06-18 → 2026-04-14 · 2 obs

● 2015-06-18 23:25:52
● 2026-04-14 12:24:58

●MXalt2.aspmx.l.google.com2015-06-18 → 2026-04-14 · 2 obs

● 2015-06-18 23:25:52
● 2026-04-14 12:24:58

●MXaspmx.l.google.com2015-06-18 → 2026-04-14 · 2 obs

● 2015-06-18 23:25:52
● 2026-04-14 12:24:58

●MXaspmx2.googlemail.com2015-06-18 → 2026-04-14 · 2 obs

● 2015-06-18 23:25:52
● 2026-04-14 12:24:58

●MXaspmx3.googlemail.com2015-06-18 → 2026-04-14 · 2 obs

● 2015-06-18 23:25:52
● 2026-04-14 12:24:58

●MXaspmx4.googlemail.com2015-06-18 → 2026-04-14 · 2 obs

● 2015-06-18 23:25:52
● 2026-04-14 12:24:58

●MXaspmx5.googlemail.com2015-06-18 → 2026-04-14 · 2 obs

● 2015-06-18 23:25:52
● 2026-04-14 12:24:58

●A46.51.244.1452026-04-10 → 2026-04-14 · 3 obs

○ 2018-09-06 00:48:58
● 2026-04-10 00:15:58
● 2026-04-14 12:24:58

○A46.51.250.2432015-06-18 → 2018-09-06 · 4 obs

● 2015-06-18 23:25:52
● 2018-09-06 00:48:58
○ 2026-04-10 00:15:58
○ 2026-04-14 12:24:58

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, g.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net...	-
h2fc-tokyo.com	dns01.muumuu-domain.com, dns02.muumuu-domain.com	2 records

✅ Authoritative Response

Server:160.251.249.62

NS records: dns01.muumuu-domain.com, dns02.muumuu-domain.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for h2fc-tokyo.com (unsigned zone)

⏱️ Timing

Total: 491ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`46.51.244.145`
NS	2	`dns02.muumuu-domain.com, dns01.muumuu-domain.com`
MX	7	`ASPMX5.GOOGLEMAIL.com (pri: 30), ALT2.ASPMX.L.GOOGLE.com (pri: 20)...`
TXT	2	`google-site-verification=7oXzn7UpTBk8wYp, v=spf1 ip4:46.51.250.243 include:_spf.go`
SOA	1	`h2fc-tokyo.com postmaster.h2fc-tokyo.com`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (dns01.muumuu-domain.com, dns02.muumuu-domain.com)

Analysis

Hierarchy

h2fc-tokyo.com is a parent of www.h2fc-tokyo.com.

Name Server Role

h2fc-tokyo.com serves as a name server for h2fc-tokyo.com.

Commonly, dns01.muumuu-domain.com and dns02.muumuu-domain.com act as name servers along with h2fc-tokyo.com.

IP Addresses

h2fc-tokyo.com points to a single IP address: 46.51.244.145.

Other host names such as eko-eko.com, utsunomiyabrex.com, evessa.com, rebnise.jp and tokyo-excellence.jp share IP numbers with h2fc-tokyo.com.

Name Servers

h2fc-tokyo.com is delegated to three name servers: h2fc-tokyo.com, dns01.muumuu-domain.com and dns02.muumuu-domain.com.

At least part of the name servers for h2fc-tokyo.com are shared with other domains, for instance noshow.jp, excitew.com, dbmemo.com, gamenavis.com and everymarch.com.