b.adingo.jp - robtex.com

b.adingo.jp

adingo.jp

DNSSEC⚠️ Not signed
A13.226.238.72πŸ‡ΊπŸ‡Έ Amazon13.226.232.0/21 - Cloudfront
A13.226.238.84πŸ‡ΊπŸ‡Έ Amazon13.226.232.0/21 - Cloudfront
A13.226.238.101πŸ‡ΊπŸ‡Έ Amazon13.226.232.0/21 - Cloudfront
A13.226.238.120πŸ‡ΊπŸ‡Έ Amazon13.226.232.0/21 - Cloudfront
NSns-59.awsdns-07.com ⭐
NSns-1404.awsdns-47.org
NSns-1968.awsdns-54.co.uk
NSns-550.awsdns-04.net
MXaspmx.l.google.com ⭐
MXalt1.aspmx.l.google.com(20)
MXalt2.aspmx.l.google.com(20)
MXaspmx2.googlemail.com(30)
MXaspmx3.googlemail.com(30)
MXaspmx4.googlemail.com(30)
MXaspmx5.googlemail.com(30)
TXTv=spf1 include:spf.voyagegr.info include:aspmx.googlemail.com include:voyage....
SOAns-59.awsdns-07.comawsdns-hostmaster@amazon.com serial=1
WOT: SAFE (50/100)
rank #786603 globally
rank #14260 in the tld
⚠️ On DNS blocklist: light, multi, pro, pro.plus, ultimate
WOT: SAFE (20/100)
πŸ“ˆ Tranco rank: #3,104

Adingo (now fluct)

Adingo was a Japanese advertising technology company specializing in internet media monetization, established in June 2008 as a wholly owned subsidiary of VOYAGE GROUP Inc. The company rebranded to fluct in 2015 and continues operations under that name.

Services

  • SSP (Sell-Side Platform) - Ad inventory management for publishers
  • Display advertising technology - Full-stack monetization solutions
  • Publisher traffic monetization - Helping media companies maximize ad revenue

Infrastructure

TypeDetails
HostingAmazon CloudFront (IPs: 18.164.174.x range)
DNSAWS Route 53 (ns-.awsdns-.com/net/org/co.uk)
EmailGoogle Workspace (aspmx.l.google.com)
SPFReferences voyagegr.info (VOYAGE GROUP)
DNSSECNot signed

Rankings & Reputation

  • Tranco Rank: 3,176 (indicating significant traffic)
  • Listed on multiple DNS blocklists (HaGeZi light, multi, pro, pro.plus, ultimate) - likely due to ad tracking/analytics scripts

Corporate

  • Headquarters: Shibuya, Tokyo, Japan
  • Parent: VOYAGE GROUP Inc. (now part of CARTA HOLDINGS)
  • Current brand: fluct (since 2015)

Same first word

DNS History

13 records (6 active, 7 former)

201820192020202120222023202420252026NSns-1263.awsdns-29.orgns-1922.awsdns-48.co.ukns-265.awsdns-33.comns-585.awsdns-09.netA13.192.40.24235.76.77.10413.192.153.20113.192.191.24913.231.30.18752.197.40.8852.199.12.7154.92.23.6954.95.183.142
●NSns-1263.awsdns-29.org2017-06-06 β†’ 2026-04-18 Β· 2 obs
● 2017-06-06 03:41:26
● 2026-04-18 10:54:58
●NSns-1922.awsdns-48.co.uk2017-06-06 β†’ 2026-04-18 Β· 2 obs
● 2017-06-06 03:41:26
● 2026-04-18 10:54:58
●NSns-265.awsdns-33.com2017-06-06 β†’ 2026-04-18 Β· 2 obs
● 2017-06-06 03:41:26
● 2026-04-18 10:54:58
●NSns-585.awsdns-09.net2017-06-06 β†’ 2026-04-18 Β· 2 obs
● 2017-06-06 03:41:26
● 2026-04-18 10:54:58
β—‹A13.192.153.2012026-02-28 β†’ 2026-02-28 Β· 4 obs
β—‹ 2017-06-06 03:41:26
● 2026-02-28 08:03:48
β—‹ 2026-03-12 10:39:42
β—‹ 2026-04-18 10:54:58
β—‹A13.192.191.2492026-03-12 β†’ 2026-03-12 Β· 4 obs
β—‹ 2026-02-28 08:03:48
● 2026-03-12 10:39:42
β—‹ 2026-04-18 10:54:56
β—‹ 2026-04-18 10:54:58
●A13.192.40.2422026-04-18 β†’ 2026-04-18 Β· 3 obs
β—‹ 2026-03-12 10:39:42
● 2026-04-18 10:54:56
● 2026-04-18 10:54:58
β—‹A13.231.30.1872026-02-28 β†’ 2026-04-18 Β· 2 obs
β—‹ 2026-02-28 08:03:48
β—‹ 2026-04-18 10:54:58
●A35.76.77.1042026-04-18 β†’ 2026-04-18 Β· 3 obs
β—‹ 2026-03-12 10:39:42
● 2026-04-18 10:54:56
● 2026-04-18 10:54:58
β—‹A52.197.40.882026-03-12 β†’ 2026-03-12 Β· 4 obs
β—‹ 2026-02-28 08:03:48
● 2026-03-12 10:39:42
β—‹ 2026-04-18 10:54:56
β—‹ 2026-04-18 10:54:58
β—‹A52.199.12.712026-02-28 β†’ 2026-02-28 Β· 4 obs
β—‹ 2017-06-06 03:41:26
● 2026-02-28 08:03:48
β—‹ 2026-03-12 10:39:42
β—‹ 2026-04-18 10:54:58
β—‹A54.92.23.692017-06-06 β†’ 2017-06-06 Β· 3 obs
● 2017-06-06 03:41:26
β—‹ 2026-02-28 08:03:48
β—‹ 2026-04-18 10:54:58
β—‹A54.95.183.1422026-02-28 β†’ 2026-04-18 Β· 2 obs
β—‹ 2026-02-28 08:03:48
β—‹ 2026-04-18 10:54:58

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
jpa.dns.jp, b.dns.jp, c.dns.jp, d.dns.jp...-
adingo.jpns-59.awsdns-07.com, ns-550.awsdns-04.net, ns-1404.awsdns-47.org, ns-1968.awsdns-54.co.uk-
b.adingo.jpns-1263.awsdns-29.org, ns-1922.awsdns-48.co.uk, ns-265.awsdns-33.com, ns-585.awsdns-09.net-

βœ… Authoritative Response

Server:205.251.194.73

NS records: ns-1263.awsdns-29.org, ns-1922.awsdns-48.co.uk, ns-265.awsdns-33.com, ns-585.awsdns-09.net

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for adingo.jp (unsigned zone)

⏱️ Timing

Total: 3116ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A235.76.77.104, 13.192.40.242
NS4ns-1263.awsdns-29.org, ns-1922.awsdns-48.co.uk...
SOA1ns-265.awsdns-33.com awsdns-hostmaster.a

Analysis

IP Addresses

b.adingo.jp resolves to two IPs: 13.192.40.242 and 35.76.77.104.

Other host names, for instance ec2-35-76-77-104.ap-northeast-1.compute.amazonaws.com, goldspotmedia.com, cosmi.io and c.adingo.jp.eimg.jp share IP numbers with b.adingo.jp.

Name Servers

b.adingo.jp is delegated to four name servers: ns-265.awsdns-33.com, ns-585.awsdns-09.net, ns-1263.awsdns-29.org and ns-1922.awsdns-48.co.uk.

b.adingo.jp at least partially shares name servers with other domains, for instance shoelakea.com, stripes.com, flexi.reviews, xpon.us and hollywood-disney.com.

These name servers are commonly used with the name servers ns-1875.awsdns-42.co.uk.

Host names with two IP numbers:

Host name ns-265.awsdns-33.com points to: 2600:9000:5301:900::1 and 205.251.193.9.

Host name ns-585.awsdns-09.net points to: 2600:9000:5302:4900::1 and 205.251.194.73.

Host name ns-1263.awsdns-29.org points to: 2600:9000:5304:ef00::1 and 205.251.196.239.

Host name ns-1922.awsdns-48.co.uk points to: 2600:9000:5307:8200::1 and 205.251.199.130.