🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`bridgecode.jp`

DNSSEC	⚠️ Not signed
NS	`lex.ns.cloudflare.com` ⭐
		A	2606:4700:58::adf5:3bc4^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lex.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c1c4^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`lex.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:21c4^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`lex.ns.cloudflare.com`
		A	108.162.193.196^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lex.ns.cloudflare.com`
		A	172.64.33.196^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lex.ns.cloudflare.com`
		A	173.245.59.196^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lex.ns.cloudflare.com`
NS	`zoe.ns.cloudflare.com`
		A	2606:4700:50::adf5:3a95^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`zoe.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c095^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`zoe.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2095^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`zoe.ns.cloudflare.com`
		A	108.162.192.149^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`zoe.ns.cloudflare.com`
		A	172.64.32.149^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`zoe.ns.cloudflare.com`
		A	173.245.58.149^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`zoe.ns.cloudflare.com`
SOA	`lex.ns.cloudflare.com`dns@cloudflare.com serial=2411022365

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

Same first word

bridgecode.xyz

bridgecode.co.uk

bridgecode.jp

bridgecode.app

bridgecode.mx

bridgecode.dev

bridgecode.net

bridgecode.in

bridgecode.kr

bridgecode.de

bridgecode.com

bridgecode.synology.me

bridgecode.co.kr

Similar names

Previous names

Next names

DNS History

2 records (2 active, 0 former)

●NSlex.ns.cloudflare.com2026-08-28 → 2026-08-30 · 2 obs

● 2026-08-28 19:43:06
● 2026-08-30 10:10:52

●NSzoe.ns.cloudflare.com2026-08-28 → 2026-08-30 · 2 obs

● 2026-08-28 19:43:06
● 2026-08-30 10:10:52

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
jp	e.dns.jp, g.dns.jp, c.dns.jp, a.dns.jp...	-
bridgecode.jp	lex.ns.cloudflare.com, zoe.ns.cloudflare.com	-

✅ Authoritative Response

Server:172.64.32.149

NS records: lex.ns.cloudflare.com, zoe.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bridgecode.jp (unsigned zone)

⏱️ Timing

Total: 731ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`lex.ns.cloudflare.com, zoe.ns.cloudflare.com`
SOA	1	`lex.ns.cloudflare.com dns.cloudflare.com`

Analysis

Name Servers

DNS delegation for bridgecode.jp points to two name servers: lex.ns.cloudflare.com and zoe.ns.cloudflare.com.

bridgecode.jp shares its NS records with other domains, for example baytreeinteractive.com, rfc-play01.com, playcabaretgames.com and two others.

bridgecode.jp has at least partial name server overlap with other domains, such as jetcasinobonus.top, intellibatching.com, sderotmedia.org.il and two others.

It is common to see these name servers used together with name servers aiden.ns.cloudflare.com and erin.ns.cloudflare.com.

DNS names with 6 IP addresses:

lex.ns.cloudflare.com has IP addresses 108.162.193.196, 172.64.33.196 and 173.245.59.196, plus 3 other.

zoe.ns.cloudflare.com has IP addresses 108.162.192.149, 172.64.32.149 and 173.245.58.149, plus 3 other.

bridgecode.jp - robtex.com

bridgecode.jp

jp