bec.tokyo - robtex.com

bec.tokyo

tokyo

DNSSEC🔒 Signed (DS record present)
NSa.gmoregistry.net
NSb.gmoregistry.net
NSk.gmoregistry.net
NSl.gmoregistry.net
SOAa.gmoregistry.netnoc@gmoregistry.net serial=1781611809

Previously MX for

Same first word

Similar names

DNS History

25 records (10 active, 15 former)

2017201820192020202120222023202420252026NShehua.ns.giantpanda.comqizai.ns.giantpanda.comns1.xtwo.ne.jpns2.xtwo.ne.jpns3.xtwo.ne.jpMXbec.tokyoA2600:3c03::f03c:95ff:fe00:29ca2600:3c03::f03c:95ff:fe91:5d522600:3c03::f03c:95ff:feed:4d4f2600:3c03::f03c:95ff:feed:cf2a45.33.83.10045.79.167.18066.175.209.17996.126.111.165139.162.174.209139.162.181.76172.104.149.86172.104.203.186172.104.251.198175.28.4.152a01:7e01::2000:dff:fec1:5cdb2a01:7e01::f03c:95ff:fe00:26922a01:7e01::f03c:95ff:fe91:5d912a01:7e01::f03c:95ff:feeb:9d4b2a01:7e01::f03c:95ff:feed:783e
NShehua.ns.giantpanda.com2026-06-12 → 2026-06-16 · 3 obs
○ 2016-12-05 01:05:42
● 2026-06-12 11:44:48
● 2026-06-16 12:29:58
NSns1.xtwo.ne.jp2016-12-05 → 2016-12-05 · 3 obs
● 2016-12-05 01:05:42
○ 2026-06-12 11:44:48
○ 2026-06-16 12:29:58
NSns2.xtwo.ne.jp2016-12-05 → 2016-12-05 · 3 obs
● 2016-12-05 01:05:42
○ 2026-06-12 11:44:48
○ 2026-06-16 12:29:58
NSns3.xtwo.ne.jp2016-12-05 → 2016-12-05 · 3 obs
● 2016-12-05 01:05:42
○ 2026-06-12 11:44:48
○ 2026-06-16 12:29:58
NSqizai.ns.giantpanda.com2026-06-12 → 2026-06-16 · 3 obs
○ 2016-12-05 01:05:42
● 2026-06-12 11:44:48
● 2026-06-16 12:29:58
MXbec.tokyo2016-12-05 → 2016-12-05 · 3 obs
● 2016-12-05 01:05:42
○ 2026-06-12 11:44:48
○ 2026-06-16 12:29:58
A139.162.174.2092026-06-12 → 2026-06-12 · 3 obs
○ 2026-06-12 11:44:48
● 2026-06-12 13:32:24
○ 2026-06-16 12:29:58
A139.162.181.762026-06-12 → 2026-06-12 · 3 obs
○ 2026-06-12 11:44:48
● 2026-06-12 13:32:24
○ 2026-06-16 12:29:58
A172.104.149.862026-06-12 → 2026-06-12 · 3 obs
○ 2026-06-12 11:44:48
● 2026-06-12 13:32:24
○ 2026-06-16 12:29:58
A172.104.203.1862026-06-12 → 2026-06-12 · 3 obs
○ 2026-06-12 11:44:48
● 2026-06-12 13:32:24
○ 2026-06-16 12:29:58
A172.104.251.1982026-06-12 → 2026-06-12 · 3 obs
○ 2026-06-12 11:44:48
● 2026-06-12 13:32:24
○ 2026-06-16 12:29:58
A175.28.4.152016-12-05 → 2016-12-05 · 3 obs
● 2016-12-05 01:05:42
○ 2026-06-12 11:44:48
○ 2026-06-16 12:29:58
A2600:3c03::f03c:95ff:fe00:29ca2026-06-12 → 2026-06-16 · 4 obs
○ 2016-12-05 01:05:42
● 2026-06-12 11:44:48
○ 2026-06-12 13:32:24
● 2026-06-16 12:29:58
A2600:3c03::f03c:95ff:fe91:5d522026-06-12 → 2026-06-16 · 4 obs
○ 2016-12-05 01:05:42
● 2026-06-12 11:44:48
○ 2026-06-12 13:32:24
● 2026-06-16 12:29:58
A2600:3c03::f03c:95ff:feed:4d4f2026-06-12 → 2026-06-16 · 4 obs
○ 2016-12-05 01:05:42
● 2026-06-12 11:44:48
○ 2026-06-12 13:32:24
● 2026-06-16 12:29:58
A2600:3c03::f03c:95ff:feed:cf2a2026-06-12 → 2026-06-16 · 4 obs
○ 2016-12-05 01:05:42
● 2026-06-12 11:44:48
○ 2026-06-12 13:32:24
● 2026-06-16 12:29:58
A2a01:7e01::2000:dff:fec1:5cdb2026-06-12 → 2026-06-12 · 3 obs
○ 2026-06-12 11:44:48
● 2026-06-12 13:32:24
○ 2026-06-16 12:29:58
A2a01:7e01::f03c:95ff:fe00:26922026-06-12 → 2026-06-12 · 3 obs
○ 2026-06-12 11:44:48
● 2026-06-12 13:32:24
○ 2026-06-16 12:29:58
A2a01:7e01::f03c:95ff:fe91:5d912026-06-12 → 2026-06-12 · 3 obs
○ 2026-06-12 11:44:48
● 2026-06-12 13:32:24
○ 2026-06-16 12:29:58
A2a01:7e01::f03c:95ff:feeb:9d4b2026-06-12 → 2026-06-12 · 3 obs
○ 2026-06-12 11:44:48
● 2026-06-12 13:32:24
○ 2026-06-16 12:29:58
A2a01:7e01::f03c:95ff:feed:783e2026-06-12 → 2026-06-12 · 3 obs
○ 2026-06-12 11:44:48
● 2026-06-12 13:32:24
○ 2026-06-16 12:29:58
A45.33.83.1002026-06-12 → 2026-06-16 · 4 obs
○ 2016-12-05 01:05:42
● 2026-06-12 11:44:48
○ 2026-06-12 13:32:24
● 2026-06-16 12:29:58
A45.79.167.1802026-06-12 → 2026-06-16 · 4 obs
○ 2016-12-05 01:05:42
● 2026-06-12 11:44:48
○ 2026-06-12 13:32:24
● 2026-06-16 12:29:58
A66.175.209.1792026-06-12 → 2026-06-16 · 4 obs
○ 2016-12-05 01:05:42
● 2026-06-12 11:44:48
○ 2026-06-12 13:32:24
● 2026-06-16 12:29:58
A96.126.111.1652026-06-12 → 2026-06-16 · 4 obs
○ 2016-12-05 01:05:42
● 2026-06-12 11:44:48
○ 2026-06-12 13:32:24
● 2026-06-16 12:29:58

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
tokyoa.gmoregistry.net, b.gmoregistry.net, k.gmoregistry.net, l.gmoregistry.net7 records
bec.tokyoqizai.ns.giantpanda.com, hehua.ns.giantpanda.com-

✅ Authoritative Response

Server:75.2.45.63

NS records: qizai.ns.giantpanda.com, hehua.ns.giantpanda.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bec.tokyo (unsigned zone)

⏱️ Timing

Total: 396ms | Queries: -

📄 Records

TypeCountSample Data
A466.175.209.179, 96.126.111.165...
AAAA42600:3c03::f03c:95ff:feed:4d4f, 2600:3c03::f03c:95ff:feed:cf2a...
NS2hehua.ns.giantpanda.com, qizai.ns.giantpanda.com
SOA1hehua.ns.giantpanda.com admin.giantpanda

📌 Glue Records Collected

Total: 7

Out-of-bailiwick: 7 (a.gmoregistry.net, b.gmoregistry.net, k.gmoregistry.net...)

Analysis

IP Addresses

bec.tokyo has 8 IP addresses — 45.33.83.100, 45.79.167.180, 66.175.209.179 and 5 more.

lmes.com, beeper.net, cutting.com.au and two other host names share IP numbers with bec.tokyo.

Name Servers

bec.tokyo is delegated to two name servers: hehua.ns.giantpanda.com and qizai.ns.giantpanda.com.

bec.tokyo uses the same name servers as several other domains — among them blackjaguar.reloader.me, kingyonlendir.link, www.redk-stron.site and two more.

There is at least partial name server overlap between bec.tokyo and other domains — tu(0x62656567)alore.com, lord2.allcheck.online, www.gizlen.biz and two more among them.

These name servers are routinely deployed together with the name servers zhenzhen.ns.giantpanda.com.

hehua.ns.giantpanda.com3.33.232.36 and qizai.ns.giantpanda.com75.2.45.63: one IP number per host name.