# dongyubin/Free-AppleId-Serve: a daily-updated shared Apple ID and proxy node repository

> The repository is a content collection, not software: a Python scraper plus a set of platform tutorials that point at daily-refreshed shared Apple IDs and free subscription addresses. It is useful if you accept the account-sharing model, and the wrong place to look if you want a maintained client or a stable node.

**dongyubin/Free-AppleId-Serve** — 2026年9月每日更新🚀苹果美区账号 APPLE ID🚀免费Shadowrocket（小火箭）共享账号,Quantumult X，圈x，stash，小火箭节点，🚀 免费订阅地址，🚀 免费节点，🚀 每天更新一次，共享节点，节点质量高可用，完全免费。免费clash订阅地址，免费翻墙，免费科学上网，免费梯子，免费ss/v2ray/trojan/clash节点,翻墙梯子，Openai ChatGPT,代理,proxy代理科学上网,TG代理,电报代理,Telegram代理,免费共享苹果外区ID,clashx Pro客户端下载,Free subscription address,使用教程

- Repository: https://github.com/dongyubin/Free-AppleId-Serve
- Website: https://help.wwkejishe.top/free-shadowrocket
- Stars: 3,516 · Forks: 207
- Language: Python
- License: not declared
- Published: 2026-09-14 · Updated: 2026-09-14 · Language: en
- Canonical page: https://hysenlabs.com/projects/dongyubin-free-appleid-serve

## What Free-AppleId-Serve actually is, and who it is for

The repository is a curated content set, not an application. Its top level holds a scraper named apple.py, a requirements.txt with three dependencies, an images directory, and roughly a dozen markdown tutorials covering Shadowrocket on iOS, ClashX Pro on macOS, Clash for Windows, Clash Verge Rev, Clash Party, v2rayN, Shadowsocks, Sing-box, and the App Store account-switching procedure itself. The README states an update date of 2026-09-14, and the last push to the repository was on 2026-09-14, so the content is refreshed rather than abandoned.

The audience is narrow and specific. It is written for readers who want a US App Store account in order to install Shadowrocket, Quantumult X, Stash, or similar clients that are not distributed in some regional storefronts, and who are willing to use an account that other people also use. The README's own framing is instructional: it describes the content as a tutorial for learning and asks readers not to use it for illegal activity. If your requirement is a private account that you control, the README points elsewhere, to a paid storefront where the description says the buyer can change the password and security questions and keep the account permanently.

## How apple.py and the daily refresh work

The mechanism visible in the repository is small. apple.py is a Python script, and requirements.txt pins beautifulsoup4==4.9.3, requests==2.25.1, and pytz. That combination indicates an HTTP fetch followed by HTML parsing, with pytz present to stamp the output in a timezone. The README's update date and the repository's last push both fall on 2026-09-14, which is consistent with a scheduled job that rewrites the account and subscription content on a daily cadence.

What the script does not do is equally important. There is no server component, no API, no database, and no client. The output is text in the repository and on the linked mirror site. The repository description mentions free subscription addresses and free nodes updated once per day, and the topics list includes clash, v2ray, shadowsocks, shadowsocksr, stash, and quantumult-x, so the refreshed content covers both account credentials and proxy subscription links.

The dependency pins are old. requests 2.25.1 and beautifulsoup4 4.9.3 date from a period well before the current releases, and pinning them exactly means the script will not pick up upstream fixes for those libraries. For a scraper that reads public HTML this is a defensible choice, since parsing behavior stays predictable, but it also means any breakage from a changed page structure lands on the maintainer rather than being absorbed by a newer parser.

## Installing the scraper and running it once

The repository does not document an install procedure in the README, so the only path is the conventional one implied by requirements.txt: create an environment and install the pinned dependencies. The script is at the repository root as apple.py.

```bash
git clone https://github.com/dongyubin/Free-AppleId-Serve.git
cd Free-AppleId-Serve
python3 -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
```

After this, requirements.txt installs beautifulsoup4, requests, and pytz at their pinned versions. If pip reports a resolution conflict, it is because the environment already holds a newer requests or beautifulsoup4 and the exact pins cannot coexist; a fresh virtual environment avoids that.

Running the script is a single command. The README does not document flags, output paths, or environment variables, so expect the script to write its results relative to the working directory.

```bash
python3 apple.py
```

Because the README is silent on what the script prints, the honest expectation is that you will inspect the repository files or the linked mirror page afterward to see the refreshed accounts and subscription addresses. There is no documented dry-run mode and no documented way to point the scraper at a different source page.

## The shared-account model is the limitation, not a footnote

Every account distributed this way is shared by an unknown number of people. The README itself acknowledges instability in this model: it states that paid shared accounts were recently taken offline because they became unstable, and it directs buyers toward individual accounts that can be modified and kept. That is the maintainer conceding the core weakness of the free tier.

Practical failure modes follow from that. A shared Apple ID can be locked or have its password changed by another user at any time, and the two-factor prompt can be triggered by someone else's login attempt rather than yours. The README also notes that when a phone number verification is required for ChatGPT-related purchases, the user must solve it themselves and that this reflects platform risk control rather than the subscription. The same logic applies here: the repository can refresh a credential, but it cannot prevent the provider from invalidating it between refreshes.

The free nodes have a comparable problem. A subscription address that is public is a subscription address that is congested, and the repository does not publish uptime figures, bandwidth guarantees, or node counts. It also does not document rollback if a refreshed list turns out worse than the previous one, so there is no supported way to revert to yesterday's addresses through the repository itself.

## What to use instead when shared credentials are not acceptable

The README's own alternative is a paid individual account from the linked shop, where the description says the buyer can change the password and security questions and use the account permanently. The difference in approach is ownership: a shared credential is rotated by a third party and revoked without notice, while a purchased individual account is under the buyer's control and survives the maintainer's refresh cycle.

For the network side, the README recommends Just My Socks, described as BandwagonHost's official service, as a way to avoid building anything yourself, and it links a separate guide in the repository. It also recommends buying a VPS and deploying a proxy stack, and includes a long prompt for a coding agent that walks through installing Marzban, Cockpit, and Netdata on a server. The distinction is between renting capacity and owning it: a free public subscription shares whatever capacity exists with everyone else reading the same page, while a VPS or a paid service allocates capacity to one account.

If the goal is only to install Shadowrocket, note that the client itself is a paid App Store purchase in most regions. The repository's guides explain how to switch store accounts to obtain it; they do not provide the app.

## Maintenance, licence and upgrade cost

The last push was on 2026-09-14, so the repository is being refreshed on the schedule the README claims. That is a statement about the content pipeline, not about the reliability of the credentials it publishes. There are no releases in the repository, so there is no versioned artifact to track and no changelog to read between updates.

The upgrade cost is low for the scraper and high for the content. Dependencies are pinned exactly, so upgrading means deliberately editing requirements.txt to newer versions and re-testing the parse against whatever page the script reads. Since the README does not document the source pages, that re-testing requires reading apple.py first.

On licensing, the top-level listing shows no LICENSE file, so the terms under which the code and the written guides may be reused are not stated in the repository. That is a real constraint if you intend to republish the tutorials or embed the scraper in your own project. This is an observation about what the repository does and does not contain, not legal advice; if redistribution matters to you, ask the maintainer directly rather than assuming a default.

## Conclusion

Adopt this only if you want a periodically refreshed pool of shared US Apple IDs and free subscription addresses and you accept that the credentials are public and the nodes are shared. Do not adopt it if you need a guaranteed private account, a supported proxy client, or anything with an SLA, because the repository ships markdown guides and a scraper, not a service. Before relying on it, check apple.py's fetch targets, confirm requirements.txt pins install cleanly on your Python version, and read the license situation, since no license file appears in the top-level listing.

## FAQ

### How do I get a free Apple ID from dongyubin/Free-AppleId-Serve?

The repository publishes shared US Apple IDs and refreshes them on a daily schedule, with the README showing an update date of 2026-09-14. It also links a mirror site that the README says carries identical content for readers who cannot reach GitHub. You do not register anything yourself; you use the credentials as published.

### How do I change the Apple ID server used by the App Store?

The repository includes a dedicated guide titled iOS-App-Store-更换苹果账号教程.md, which walks through switching the store account on iOS. The README's table of contents also links platform-specific client tutorials for Shadowrocket, ClashX Pro, Clash for Windows, v2rayN and others.

### Can I get an Apple ID and password for free from this project?

Yes, in the sense that the repository publishes shared account credentials rather than selling them. The README describes these as shared accounts and separately notes that paid shared accounts were taken offline for instability, pointing buyers toward individual accounts that can be modified and kept.

### Can I get a free Apple ID with games from this repository?

The repository does not document which apps or games the shared accounts can access beyond the proxy clients it is built around, such as Shadowrocket, Quantumult X and Stash. The README does not make any claim about game availability, so that cannot be confirmed from the repository.

## Sources

- [dongyubin/Free-AppleId-Serve on GitHub](https://github.com/dongyubin/Free-AppleId-Serve)
- [Issues](https://github.com/dongyubin/Free-AppleId-Serve/issues)
- [Project website](https://help.wwkejishe.top/free-shadowrocket)
- [README](https://github.com/dongyubin/Free-AppleId-Serve/blob/main/README.md)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/dongyubin-free-appleid-serve