App SupplyIndex Check an app
C70 / 100

MIXI, Inc.

family-album.com/app-ads.txt · 4 apps · iOS · 1,390 seller lines · checked Nov 16, 2026

16 lines to fix. Three steps take this file from C 70 to B 82.

1,390 seller lines in family-album.com/app-ads.txt; 929 could be checked against the ad systems' sellers.json. Main finding: Seller IDs not listed in the ad system's sellers.json.

app-ads.txtLines from steps 1–3
339districtm.io, 101649, RESELLER, 3fd707be9c4527c3Remove: districtm.io doesn't resolve. No partner contact needed.
355engagebdr.com, 10181, RESELLERRemove: engagebdr.com doesn't resolve. No partner contact needed.
356engagebdr.com, 10252, RESELLERRemove: engagebdr.com doesn't resolve. No partner contact needed.
+ 6 more lines for ad systems that don't resolve
+OWNERDOMAIN=<your company domain>Add this line, with the domain your company uses in sellers.json.
107algorix.co, 60332, DIRECT, 5b394c12fea27a1dConfirm with the partner: the same account is marked DIRECT by 4 different companies. If the account isn't yours, use RESELLER.
933rubiconproject.com, 15268, DIRECT, 0bfd66d529a55807Confirm with the partner: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 179 different companies. If the account isn't yours, use RESELLER.
953rubiconproject.com, 22884, DIRECT, 0bfd66d529a55807Confirm with the partner: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 86 different companies. If the account isn't yours, use RESELLER.
+ 4 more DIRECT lines to confirm

What to change

Easiest first. Points are estimates, assuming every line in a step is fixed.

  1. Remove 9 lines for ad system domains that didn't resolve. No partner contact needed.+1 → 71
  2. Add OWNERDOMAIN=<your company domain> to the file.+2 → 73
  3. Confirm 7 DIRECT lines with the partners that supplied them; use RESELLER where the account isn't yours.+9 → B 82
  4. Ask partners about 116 seller IDs missing from their sellers.json; remove lines for closed accounts.+10 → A 92
  5. Add OWNERDOMAIN, or confirm 12 DIRECT accounts registered to another domain.+8 → A 100
Re-check now

Findings

Each finding lists the exact lines involved. Findings are automated observations of public files as of Nov 16, 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

116 −10 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. Full guide →
Evidence (25 of 116)
line 6      acexchange.co.kr, 1024314629, RESELLER
             → sellers_json: https://acexchange.co.kr/sellers.json
line 7      acexchange.co.kr, 1317287336, 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 177    appsheep.com, 14441a46f4f44c9185886bbfbd44bd5a, RESELLER
             → sellers_json: https://appsheep.com/sellers.json
line 179    appsheep.com, 27dee787560b471cafde1e55d87bc75b, RESELLER
             → sellers_json: https://appsheep.com/sellers.json
line 188    appsheep.com, fc7556810c904b029cd14668a5ee42e3, RESELLER
             → sellers_json: https://appsheep.com/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

Showing 25 of 116. The Copy button copies all 116 lines.

warning

DIRECT lines inconsistent with public data

7 −9 pts

The IAB ads.txt specification: "A value of ‘DIRECT’ indicates that the Publisher (content owner) directly controls the account." 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 companies with different owner domains. 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. Full guide →
Evidence (7)
line 107    algorix.co, 60332, DIRECT, 5b394c12fea27a1d
             → observed: the same account is marked DIRECT by 4 different companies
line 933    rubiconproject.com, 15268, DIRECT, 0bfd66d529a55807
             → observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 179 different companies  name in sellers.json: Unruly Group LTD  domain in sellers.json: unrulymedia.com
line 953    rubiconproject.com, 22884, DIRECT, 0bfd66d529a55807
             → observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 86 different companies  name in sellers.json: Google  domain in sellers.json: google.com
line 1022   singularads.com, 445896, DIRECT
             → observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 4 different companies  name in sellers.json: Topon  domain in sellers.json: toponad.com
line 1025   smaato.com, 1100004890, DIRECT, 07bcf65f187117b4
             → observed: the same account is marked DIRECT by 247 different companies  name in sellers.json: Smaato Managed  domain in sellers.json: smaato.com
line 1041   smaato.com, 1100057546, DIRECT, 07bcf65f187117b4
             → observed: the same account is marked DIRECT by 89 different companies
line 1135   synacor.com, 82460, DIRECT, e108f11b2cdf7d5b
             → observed: the same account is marked DIRECT by 63 different companies
warning

Ad system domains that didn't resolve at crawl time

9 −1 pts

These ad system domains returned no DNS address at crawl time, checked twice (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. Full guide →
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 904    reforge.in, 107, RESELLER
             → ad_system: reforge.in
line 905    reforge.in, 353, RESELLER
             → ad_system: reforge.in
line 1380   ylhglobal.com, 1930587443, RESELLER
             → ad_system: ylhglobal.com
info

DIRECT accounts registered to another domain

12 −8 pts

The IAB ads.txt specification: "A value of ‘DIRECT’ indicates that the Publisher (content owner) directly controls the account." For these DIRECT lines, the ad system's own sellers.json lists the account under another company's domain. Allowed when that domain belongs to the same company; add OWNERDOMAIN to make that explicit.

How to fixIf the account is yours under another domain, declare it with OWNERDOMAIN=<that domain>; otherwise mark it RESELLER. Full guide →
Evidence (12)
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 836    pubmatic.com, 162473, DIRECT, 5d62403b186f2ace
             → domain in sellers.json: tbsholdings.co.jp  name in sellers.json: Tokyo Broadcasting System Television, Inc. (TBS)
line 847    pubmatic.com, 163894, DIRECT, 5d62403b186f2ace
             → domain in sellers.json: fujitv.co.jp  name in sellers.json: Fuji Television Network, Inc.
line 851    pubmatic.com, 164323, DIRECT, 5d62403b186f2ace
             → domain in sellers.json: mbs.jp  name in sellers.json: MAINICHI BROADCASTING SYSTEM, INC.
line 853    pubmatic.com, 164849, DIRECT, 5d62403b186f2ace
             → domain in sellers.json: asahi.co.jp  name in sellers.json: Asahi Television Broadcasting Corporation 
line 854    pubmatic.com, 165107, DIRECT, 5d62403b186f2ace
             → domain in sellers.json: tv-tokyo.co.jp  name in sellers.json: TV TOKYO Communications Corporation (VOXX-oRTB)
line 860    pubmatic.com, 165447, DIRECT, 5d62403b186f2ace
             → domain in sellers.json: ytv.co.jp  name in sellers.json: YOMIURI TELECASTING CORPORATION (YTV)
line 864    pubmatic.com, 165877, DIRECT, 5d62403b186f2ace
             → domain in sellers.json: ktv.jp  name in sellers.json: Kansai Television Co. Ltd.
line 1163   themediagrid.com, SMXC6T, DIRECT, 35d5010d7789b49d
             → domain in sellers.json: amoad.com  name in sellers.json: CyberAgent,Inc.
line 1259   unity.com, 1241211, DIRECT, 96cabb5fbdde37a7
             → domain in sellers.json: namepara.com  name in sellers.json: fluct
line 1387   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. Full guide →
info

Ad systems whose sellers.json we couldn't read

218

We couldn't read a sellers.json for these ad systems at crawl time (no file, invalid JSON, empty, or automated access refused), so these lines weren't verified. No points are deducted.

How to fixAsk the partner to publish sellers.json; until then buyers can't verify that path. Full guide →
Evidence (25 of 218)
line 5      acd.op.hicloud.com, PUB_HW_1003, RESELLER
             → sellers_json: HTTP 404
line 13     adcolony.com, 0a0f72cd66122f31, RESELLER, 1ad675c9de6b5176
             → sellers_json: HTTP 404
line 14     adcolony.com, 1efc6603710003ea, RESELLER, 1ad675c9de6b5176
             → sellers_json: HTTP 404
line 15     adcolony.com, 29b7f4a14dc689eb, RESELLER, 1ad675c9de6b5176
             → sellers_json: HTTP 404
line 16     adcolony.com, 7d04a18a58085918, RESELLER, 1ad675c9de6b5176
             → sellers_json: HTTP 404
line 17     adcolony.com, 801e49d1be83b5f9, RESELLER, 1ad675c9de6b5176
             → sellers_json: HTTP 404
line 18     adcolony.com, c490f6e7399a25d6, RESELLER, 1ad675c9de6b5176
             → sellers_json: HTTP 404
line 76     adtiming.com, a-126, RESELLER, bf66753b8f380142
             → sellers_json: HTTP 404
line 78     advertising.com, 23089, RESELLER
             → sellers_json: HTTP 404
line 79     advertising.com, 26154, RESELLER
             → sellers_json: HTTP 404
line 80     advertising.com, 28038, RESELLER
             → sellers_json: HTTP 404
line 81     advertising.com, 28246, RESELLER
             → sellers_json: HTTP 404
line 82     advertising.com, 28605, RESELLER
             → sellers_json: HTTP 404
line 83     advertising.com, 28886, RESELLER
             → sellers_json: HTTP 404
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: file is not valid JSON
line 113    aol.com, 58935, RESELLER, e1a5b5b6e3255540
             → sellers_json: HTTP 404
line 114    aol.com, 59025, RESELLER, e1a5b5b6e3255540
             → sellers_json: HTTP 404
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
line 130    appnexus.com, 11470, RESELLER
             → sellers_json: HTTP 403 to automated requests

Showing 25 of 218. The Copy button copies all 218 lines.

info

Same line listed more than once

11

Common when several partners' blocks include the same seat (for example, two mediation partners that both resell through one exchange account). Buyers treat repeated lines as one, so there's no effect on verification and no points are deducted.

How to fixNothing required. Keeping each partner's block intact makes it easy to remove a partner later. Full guide →
Evidence (11)
line 149    appnexus.com, 13293, RESELLER
             → listed: 2 times  partner blocks: no comments
line 165    appnexus.com, 6849, RESELLER
             → listed: 2 times  partner blocks: no comments
line 277    contextweb.com, 558511, RESELLER
             → listed: 2 times  partner blocks: no comments
line 523    inmobi.com, 9e311c7a68e94888aac7fbb4272381e2, RESELLER
             → listed: 2 times  partner blocks: no comments
line 682    onetag.com, 8668c16092f01e8, RESELLER
             → listed: 2 times  partner blocks: no comments
line 688    onlinemediasolutions.com, 29556, RESELLER
             → listed: 2 times  partner blocks: no comments
line 798    pubmatic.com, 159277, RESELLER
             → listed: 2 times  partner blocks: no comments
line 800    pubmatic.com, 159382, RESELLER
             → listed: 2 times  partner blocks: no comments
line 934    rubiconproject.com, 15268, RESELLER
             → listed: 2 times  partner blocks: no comments
line 1051   smartadserver.com, 3232, RESELLER
             → listed: 2 times  partner blocks: no comments
line 1066   smartadserver.com, 4284, RESELLER
             → listed: 2 times  partner blocks: no comments

Showing 11 of 11. The Copy button copies all 22 lines.

4 app-ads.txt files

The report above is for family-album.com, the file most of these apps use. Each file is checked and graded on its own. Grouped as one publisher because:

  • same App Store developer account
GradeScoreFileAppsLinesMain finding
C 70 family-album.com 1 1,390 Seller IDs not listed in the ad system's sellers.json
C 70 mitene.us 1 1,390 Seller IDs not listed in the ad system's sellers.json
— – mixi.jp 1 6 Too few verifiable lines to grade
— – photo-nenga.jp 1 1 Too few verifiable lines to grade

Apps

4 apps in this index, in 4 studios or files, each with its own app-ads.txt and grade. 1 is in this week's US charts.

C MIXI, Inc. family-album.com · 1 app · 70/100

AppGenreStoreIn the charts
FamilyAlbum: Share Baby Photos Lifestyle iOS #76

C MIXI, Inc. mitene.us · 1 app · 70/100

AppGenreStoreIn the charts
みてねみまもりGPS Lifestyle iOS —

— MIXI, Inc. mixi.jp · 1 app

AppGenreStoreIn the charts
mixi - Community of Hobbies! Social Networking iOS —

— MIXI, Inc. photo-nenga.jp · 1 app

AppGenreStoreIn the charts
年賀状 2027 スマホで写真年賀状 アプリで年賀状作成 Lifestyle iOS —

About this file

app-ads.txt
https://family-album.com/app-ads.txt · 200
Score
C 70/100 · 1,390 lines · 929 checked against sellers.json
Grouping
4 files, grouped on the evidence listed above. Store names alone never group publishers.
Checked
Nov 16, 2026

Is this your file?

Changed it? Check any of these apps live; this page updates weekly. Think something here is wrong? Request a correction.

Check an app