App Supply Index Monitor my app
iOS · MIXI, Inc.

FamilyAlbum: Share Baby Photos

Developer URL
https://family-album.com/
app-ads.txt
https://family-album.com/app-ads.txt · 200
Checked
Oct 7, 2026
C
67/100

1,380 lines · 892 verified against sellers.json

Findings

Each finding lists the exact lines involved. Findings are automated observations of public files as of Oct 7, 2026. They describe file contents, not the intent or conduct of any company.

warning

Seller IDs not listed in the ad system's sellers.json

136 −12 pts

The ad system's current sellers.json doesn't list these accounts, so buyers that validate the chain can't match them. Common causes are closed accounts or former partners.

How to fixAsk each partner whether the account is still active and request their current lines; remove lines for closed accounts.
Evidence (25 of 136)
line 6      acexchange.co.kr, 1024314629, RESELLER
             → sellers_json: https://acexchange.co.kr/sellers.json
line 38     adingo.jp, 31358, RESELLER
             → sellers_json: https://adingo.jp/sellers.json
line 50     admanmedia.com, 621, RESELLER
             → sellers_json: https://admanmedia.com/sellers.json
line 51     admanmedia.com, 894, RESELLER
             → sellers_json: https://admanmedia.com/sellers.json
line 61     admixer.net, 2f833c20-7378-4b86-9b73-a2b56263d4d4, RESELLER
             → sellers_json: https://admixer.net/sellers.json
line 62     admixer.net, 3bc509b2-6568-4bd8-a997-9859ba0c9118, RESELLER
             → sellers_json: https://admixer.net/sellers.json
line 65     admixer.net, 70590d13-5632-41d5-8a78-76bc239c528c, RESELLER
             → sellers_json: https://admixer.net/sellers.json
line 85     adview.com, 32076181, RESELLER, 1b2cc038a11ea319
             → sellers_json: https://adview.com/sellers.json
line 100    algorix.co, 54510, RESELLER, 5b394c12fea27a1d
             → sellers_json: https://algorix.co/sellers.json
line 103    algorix.co, 60095, RESELLER, 5b394c12fea27a1d
             → sellers_json: https://algorix.co/sellers.json
line 104    algorix.co, 60097, RESELLER, 5b394c12fea27a1d
             → sellers_json: https://algorix.co/sellers.json
line 107    algorix.co, 60332, DIRECT, 5b394c12fea27a1d
             → sellers_json: https://algorix.co/sellers.json
line 190    aralego.com, par-AA7B236BA32DD484C838E249362437B8, RESELLER
             → sellers_json: https://aralego.com/sellers.json
line 192    aralego.com, par-E2B2BB3E89BE87A2F774B768BEED62A2, RESELLER
             → sellers_json: https://aralego.com/sellers.json
line 204    axonix.com, 59089, RESELLER, bc385f2b4a87b721
             → sellers_json: https://axonix.com/sellers.json
line 206    axonix.com, 59150, RESELLER, bc385f2b4a87b721
             → sellers_json: https://axonix.com/sellers.json
line 216    betweendigital.com, 43843, RESELLER
             → sellers_json: https://betweendigital.com/sellers.json
line 225    bid-matrix.com, 7a33a9718c7ee898, RESELLER
             → sellers_json: https://bid-matrix.com/sellers.json
line 227    bidease.com, bidease_seller_34, RESELLER
             → sellers_json: https://bidease.com/sellers.json
line 238    bidmachine.io, 114, RESELLER
             → sellers_json: https://bidmachine.io/sellers.json
line 264    caerulus.io, 3320-44758, RESELLER
             → sellers_json: https://caerulus.io/sellers.json
line 267    castify.ai, 1210421, RESELLER
             → sellers_json: https://castify.ai/sellers.json
line 270    chocolateplatform.com, 14637, RESELLER, 49a66ce31a704197
             → sellers_json: https://chocolateplatform.com/sellers.json
line 348    e-planning.net, ea9874674191f1ff, RESELLER, c1ba615865ed87b2
             → sellers_json: https://e-planning.net/sellers.json
line 408    gitberry.com, 42knb, RESELLER
             → sellers_json: https://gitberry.com/sellers.json
warning

DIRECT lines inconsistent with public data

7 −9 pts

The ads.txt specification defines DIRECT as an account the publisher directly controls. For these lines, either the ad system's own sellers.json lists the account as INTERMEDIARY, or the same account is marked DIRECT in the files of 3 or more unrelated companies. Either way, the public data does not support the DIRECT label. Buyers that use DIRECT labels in supply-path decisions may treat these lines differently.

How to fixUse DIRECT only for accounts your company controls. Confirm with each partner whether the account is yours; if it isn't, the specification calls for RESELLER.
Evidence (7)
line 107    algorix.co, 60332, DIRECT, 5b394c12fea27a1d
             → observed: the same account is marked DIRECT by 3 different companies
line 925    rubiconproject.com, 15268, DIRECT, 0bfd66d529a55807
             → observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 112 different companies  name in sellers.json: Unruly Group LTD  domain in sellers.json: unrulymedia.com
line 945    rubiconproject.com, 22884, DIRECT, 0bfd66d529a55807
             → observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 43 different companies  name in sellers.json: Google  domain in sellers.json: google.com
line 1014   singularads.com, 445896, DIRECT
             → observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: Topon  domain in sellers.json: toponad.com
line 1017   smaato.com, 1100004890, DIRECT, 07bcf65f187117b4
             → observed: the same account is marked DIRECT by 160 different companies
line 1033   smaato.com, 1100057546, DIRECT, 07bcf65f187117b4
             → observed: the same account is marked DIRECT by 46 different companies
line 1127   synacor.com, 82460, DIRECT, e108f11b2cdf7d5b
             → observed: the same account is marked DIRECT by 47 different companies
warning

Lines for ad system domains that don't resolve

9 −1 pts

These ad system domains don't resolve (the domain may be retired, merged or misspelled). The lines can't be validated, and if the domain is registered again, its new holder would appear authorized.

How to fixRemove these lines. If the domain is registered again, its new holder would appear authorized by your file.
Evidence (9)
line 339    districtm.io, 101649, RESELLER, 3fd707be9c4527c3
             → ad_system: districtm.io
line 355    engagebdr.com, 10181, RESELLER
             → ad_system: engagebdr.com
line 356    engagebdr.com, 10252, RESELLER
             → ad_system: engagebdr.com
line 357    engagebdr.com, 10423, RESELLER
             → ad_system: engagebdr.com
line 368    fivecdm.com, 115622, DIRECT
             → ad_system: fivecdm.com
line 369    fivecdm.com, 16983206, RESELLER
             → ad_system: fivecdm.com
line 896    reforge.in, 107, RESELLER
             → ad_system: reforge.in
line 897    reforge.in, 353, RESELLER
             → ad_system: reforge.in
line 1370   ylhglobal.com, 1930587443, RESELLER
             → ad_system: ylhglobal.com
info

DIRECT accounts registered to another domain

13 −8 pts

Allowed when the domain belongs to the same company; add OWNERDOMAIN to make that explicit. Otherwise these accounts may belong to someone else.

How to fixIf the account is yours under another domain, declare it with OWNERDOMAIN=<that domain>; otherwise mark it RESELLER.
Evidence (13)
line 10     ad-generation.jp, 14139, DIRECT, 7f4ea9029ac04e53
             → domain in sellers.json: mixi.co.jp  name in sellers.json: 株式会社MIXI_家族アルバムみてね
line 39     adingo.jp, 31907, DIRECT
             → domain in sellers.json: mixi.co.jp  name in sellers.json: 株式会社MIXI(みてね)
line 415    google.com, pub-4108518876318205, DIRECT, f08c47fec0942fa0
             → domain in sellers.json: mixi.co.jp  name in sellers.json: Mixi Mitene
line 829    pubmatic.com, 162473, DIRECT, 5d62403b186f2ace
             → domain in sellers.json: tbsholdings.co.jp  name in sellers.json: Tokyo Broadcasting System Television, Inc. (TBS)
line 840    pubmatic.com, 163894, DIRECT, 5d62403b186f2ace
             → domain in sellers.json: fujitv.co.jp  name in sellers.json: Fuji Television Network, Inc.
line 844    pubmatic.com, 164323, DIRECT, 5d62403b186f2ace
             → domain in sellers.json: mbs.jp  name in sellers.json: MAINICHI BROADCASTING SYSTEM, INC.
line 846    pubmatic.com, 164849, DIRECT, 5d62403b186f2ace
             → domain in sellers.json: asahi.co.jp  name in sellers.json: Asahi Television Broadcasting Corporation 
line 847    pubmatic.com, 165107, DIRECT, 5d62403b186f2ace
             → domain in sellers.json: tv-tokyo.co.jp  name in sellers.json: TV TOKYO Communications Corporation (VOXX-oRTB)
line 853    pubmatic.com, 165447, DIRECT, 5d62403b186f2ace
             → domain in sellers.json: ytv.co.jp  name in sellers.json: YOMIURI TELECASTING CORPORATION (YTV)
line 857    pubmatic.com, 165877, DIRECT, 5d62403b186f2ace
             → domain in sellers.json: ktv.jp  name in sellers.json: Kansai Television Co. Ltd.
line 1155   themediagrid.com, SMXC6T, DIRECT, 35d5010d7789b49d
             → domain in sellers.json: amoad.com  name in sellers.json: CyberAgent,Inc.
line 1249   unity.com, 1241211, DIRECT, 96cabb5fbdde37a7
             → domain in sellers.json: namepara.com  name in sellers.json: fluct
line 1377   zmaticoo.com, 116791, DIRECT
             → domain in sellers.json: nordot.app  name in sellers.json: Nordot
info

No OWNERDOMAIN declared

1 −2 pts

app-ads.txt 1.1 recommends OWNERDOMAIN so buyers can match DIRECT accounts to the owner.

How to fixAdd OWNERDOMAIN=<your company domain> to the file.
info

Duplicate lines

11 −1 pts

Harmless but a sign of copy-paste maintenance.

How to fixRemove duplicates; keep one copy of each line.
Evidence (11)
ad_system: appnexus.com  seller_id: 13293  relationship: RESELLER
ad_system: appnexus.com  seller_id: 6849  relationship: RESELLER
ad_system: contextweb.com  seller_id: 558511  relationship: RESELLER
ad_system: inmobi.com  seller_id: 9e311c7a68e94888aac7fbb4272381e2  relationship: RESELLER
ad_system: onetag.com  seller_id: 8668c16092f01e8  relationship: RESELLER
ad_system: onlinemediasolutions.com  seller_id: 29556  relationship: RESELLER
ad_system: pubmatic.com  seller_id: 159277  relationship: RESELLER
ad_system: pubmatic.com  seller_id: 159382  relationship: RESELLER
ad_system: rubiconproject.com  seller_id: 15268  relationship: RESELLER
ad_system: smartadserver.com  seller_id: 3232  relationship: RESELLER
ad_system: smartadserver.com  seller_id: 4284  relationship: RESELLER
info

Ad systems without a public sellers.json

298

The ad system doesn't publish a readable sellers.json, so nobody can verify these lines. That's the ad system's gap, not the app's, so no points are deducted.

How to fixAsk the partner to publish sellers.json; until then buyers can't verify that path.
Evidence (25 of 298)
line 5      acd.op.hicloud.com, PUB_HW_1003, RESELLER
             → sellers_json: HTTP 404
line 13     adcolony.com, 0a0f72cd66122f31, RESELLER, 1ad675c9de6b5176
             → sellers_json: returns a web page, not a sellers.json file
line 14     adcolony.com, 1efc6603710003ea, RESELLER, 1ad675c9de6b5176
             → sellers_json: returns a web page, not a sellers.json file
line 15     adcolony.com, 29b7f4a14dc689eb, RESELLER, 1ad675c9de6b5176
             → sellers_json: returns a web page, not a sellers.json file
line 16     adcolony.com, 7d04a18a58085918, RESELLER, 1ad675c9de6b5176
             → sellers_json: returns a web page, not a sellers.json file
line 17     adcolony.com, 801e49d1be83b5f9, RESELLER, 1ad675c9de6b5176
             → sellers_json: returns a web page, not a sellers.json file
line 18     adcolony.com, c490f6e7399a25d6, RESELLER, 1ad675c9de6b5176
             → sellers_json: returns a web page, not a sellers.json file
line 76     adtiming.com, a-126, RESELLER, bf66753b8f380142
             → sellers_json: HTTP 404
line 78     advertising.com, 23089, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 79     advertising.com, 26154, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 80     advertising.com, 28038, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 81     advertising.com, 28246, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 82     advertising.com, 28605, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 83     advertising.com, 28886, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 87     adx-dra.op.hicloud.com, PUB_HW_1003, RESELLER
             → sellers_json: HTTP 404
line 88     adx-dre.op.hicloud.com, PUB_HW_1003, RESELLER
             → sellers_json: HTTP 404
line 89     adx-drru.op.hicloud.com, PUB_HW_1003, RESELLER
             → sellers_json: HTTP 404
line 98     alaska-gaming.com, 19879, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 113    aol.com, 58935, RESELLER, e1a5b5b6e3255540
             → sellers_json: HTTP 404
line 114    aol.com, 59025, RESELLER, e1a5b5b6e3255540
             → sellers_json: HTTP 404
line 115    apester.com, 2212, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 126    appnexus.com, 1019, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403 to automated requests
line 127    appnexus.com, 10617, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 128    appnexus.com, 10824, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 129    appnexus.com, 11450, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403 to automated requests

Is this your app?

Get the full evidence list, a cleaned app-ads.txt, and alerts when partners' accounts change. Think something here is wrong? Request a correction.

Monitor this app