repubrew.com - dns.ninja

`repubrew.com`

DNSSEC	⚠️ Not signed
A	219.99.174.101^{🇯🇵 FUTURE219.99.168.0/21 FS CIDR BLOCK ORIGIN-AS23824-interim}
A	219.99.174.102^{🇯🇵 FUTURE219.99.168.0/21 FS CIDR BLOCK ORIGIN-AS23824-interim}
NS	`ns0.future-s.com` ⭐
		A	219.99.167.170^{🇯🇵 FUTURE219.99.160.0/21 FS CIDR BLOCK ORIGIN-AS23824-interim}
			PTR	`ns0.future-s.com`
NS	`ns2.future-s.com`
		A	219.99.167.171^{🇯🇵 FUTURE219.99.160.0/21 FS CIDR BLOCK ORIGIN-AS23824-interim}
			PTR	`ns2.future-s.com`
NS	`ns3.future-s.com`
		A	219.99.161.8^{🇯🇵 FUTURE219.99.160.0/21 FS CIDR BLOCK ORIGIN-AS23824-interim}
			PTR	`ns3.future-s.com`
NS	`ns4.future-s.com`
		A	219.99.172.9^{🇯🇵 FUTURE219.99.168.0/21 FS CIDR BLOCK ORIGIN-AS23824-interim}
			PTR	`ns4.future-s.com`
NS	`ns5.future-s.com`
		A	219.99.172.10^{🇯🇵 FUTURE219.99.168.0/21 FS CIDR BLOCK ORIGIN-AS23824-interim}
			PTR	`ns5.future-s.com`
MX	`sagw.fsi.ne.jp` ⭐
		A	219.99.161.47^{🇯🇵 FUTURE219.99.160.0/21 FS CIDR BLOCK ORIGIN-AS23824-interim}
			PTR	`sagw21.fsi.ne.jp`
		A	219.99.164.25^{🇯🇵 FUTURE219.99.160.0/21 FS CIDR BLOCK ORIGIN-AS23824-interim}
			PTR	`sagw22.fsi.ne.jp`
		A	219.99.167.85^{🇯🇵 FUTURE219.99.160.0/21 FS CIDR BLOCK ORIGIN-AS23824-interim}
			PTR	`sagw23.fsi.ne.jp`
TXT	`v=spf1 include:spfgw.fsi.ne.jp include:spf.q-send.jp ~all`
SOA	`ns0.future-s.com`dnsadmin@future-s.com 2024-12-10 #3

`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=1786729464

Same first word

repubrew.com

Similar names

brewpure.com

purebrew.com

purebrew.ca

DNS History

12 records (8 active, 4 former)

○NSdns01.gmoserver.jp2017-01-04 → 2018-09-02 · 4 obs

● 2017-01-04 18:16:06
● 2018-09-02 19:51:38
○ 2026-02-24 20:58:38
○ 2026-08-14 18:00:36

○NSdns02.gmoserver.jp2017-01-04 → 2018-09-02 · 4 obs

● 2017-01-04 18:16:06
● 2018-09-02 19:51:38
○ 2026-02-24 20:58:38
○ 2026-08-14 18:00:36

●NSns0.future-s.com2026-02-24 → 2026-08-14 · 3 obs

○ 2018-09-02 19:51:38
● 2026-02-24 20:58:38
● 2026-08-14 18:00:36

●NSns2.future-s.com2026-02-24 → 2026-08-14 · 3 obs

○ 2018-09-02 19:51:38
● 2026-02-24 20:58:38
● 2026-08-14 18:00:36

●NSns3.future-s.com2026-02-24 → 2026-08-14 · 3 obs

○ 2018-09-02 19:51:38
● 2026-02-24 20:58:38
● 2026-08-14 18:00:36

●NSns4.future-s.com2026-02-24 → 2026-08-14 · 3 obs

○ 2018-09-02 19:51:38
● 2026-02-24 20:58:38
● 2026-08-14 18:00:36

●NSns5.future-s.com2026-02-24 → 2026-08-14 · 3 obs

○ 2018-09-02 19:51:38
● 2026-02-24 20:58:38
● 2026-08-14 18:00:36

○MXmx2.gmoserver.jp2017-01-04 → 2018-09-02 · 4 obs

● 2017-01-04 18:16:06
● 2018-09-02 19:51:38
○ 2026-02-24 20:58:38
○ 2026-08-14 18:00:36

●MXsagw.fsi.ne.jp2026-02-24 → 2026-08-14 · 3 obs

○ 2018-09-02 19:51:38
● 2026-02-24 20:58:38
● 2026-08-14 18:00:36

○A210.172.183.492017-01-04 → 2018-09-02 · 4 obs

● 2017-01-04 18:16:06
● 2018-09-02 19:51:38
○ 2026-02-24 20:58:38
○ 2026-08-14 18:00:36

●A219.99.174.1012026-02-24 → 2026-08-14 · 3 obs

○ 2018-09-02 19:51:38
● 2026-02-24 20:58:38
● 2026-08-14 18:00:36

●A219.99.174.1022026-02-24 → 2026-08-14 · 3 obs

○ 2018-09-02 19:51:38
● 2026-02-24 20:58:38
● 2026-08-14 18:00:36

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
repubrew.com	ns2.future-s.com, ns3.future-s.com, ns4.future-s.com, ns5.future-s.com	4 records

✅ Authoritative Response

Server:219.99.172.10

NS records: ns2.future-s.com, ns3.future-s.com, ns4.future-s.com, ns5.future-s.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for repubrew.com (unsigned zone)

⏱️ Timing

Total: 494ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`219.99.174.101, 219.99.174.102`
NS	4	`ns5.future-s.com, ns2.future-s.com...`
MX	1	`sagw.fsi.ne.jp (pri: 10)`
TXT	1	`v=spf1 include:spfgw.fsi.ne.jp include:s`
SOA	1	`ns0.future-s.com dnsadmin.future-s.com`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns2.future-s.com, ns3.future-s.com, ns4.future-s.com...)

Analysis

IP Addresses

repubrew.com has two IP addresses: 219.99.174.101 and 219.99.174.102

hms-watchstore.com, someplace-else.com, mansaw.net plus two other host names have IP numbers in common with repubrew.com.

Name Servers

Five name servers handle delegation for repubrew.com: ns0.future-s.com, ns2.future-s.com, ns3.future-s.com and two others.

At least some of repubrew.com's name servers are shared with other domains, for example shofuan-shop.com, sparklingmall.jp, ah-inabaya.jp and two more.

It is common for these name servers to be used in conjunction with the name servers ns4.future-s.com, ns5.future-s.com and ns1.future-s.com.

Host names resolving to a single IP address:

ns0.future-s.com resolves to 219.99.167.170.

ns2.future-s.com resolves to 219.99.167.171.

ns3.future-s.com resolves to 219.99.161.8.

ns4.future-s.com resolves to 219.99.172.9.

ns5.future-s.com resolves to 219.99.172.10.

Mail Servers

repubrew.com uses one mail server — sagw.fsi.ne.jp.

The mail server setup of repubrew.com matches that of other domains such as kamakuragoro.co.jp, data-gate.com, bebeimport.jp and two others.

sagw.fsi.ne.jp resolves to three IP numbers — 219.99.161.47, 219.99.164.25 and 219.99.167.85.