Security report for iloader.org
iloader · Technology
Low risk. 2 critical or high findings in Email security.
iloader is an independent IPA app library service catering to iPhone and iPad users who utilize sideloading tools to install apps outside the official App Store. The website provides a curated catalog of IPA files, detailed compatibility information, and installation guidance, supporting users in discovering and safely downloading iOS apps. The business model is based on a one-time payment granting access to approved IPA files for a defined period, with no automatic renewals. The service emphasizes transparency, user education, and compliance with licensing and distribution rights.
Scanned
NIS2 and GDPR posture
- NIS2 outside view
- 60/ 100 · Medium
- GDPR outside view
- 100/ 100 · Low
- Checks completed
- 9of 9
NIS2 Art. 21(2)
- (a) Risk analysis and security policies: Not visible from outside
- (b) Incident handling: One indicator
- (c) Business continuity, backups and crisis management: Not visible from outside
- (d) Supply chain security: Not visible from outside
- (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
- (f) Assessing the effectiveness of security measures: Not visible from outside
- (g) Cyber hygiene and security training: Not visible from outside
- (h) Cryptography and encryption: Partly checked
- (i) HR security, access control and asset management: One indicator
- (j) Multi-factor authentication and secured communications: Not visible from outside
The NIS2 figure counts only evidence anyone can see from the internet. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.
GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.
Priority findings
2 findings rated critical or high. Fix these first.
Email security
SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.
- High
No SPF record found
iloader.org publishes no SPF record, so receiving servers cannot tell which servers may send mail as this domain.
What to do: Publish one TXT record listing your mail providers, for example "v=spf1 include:_spf.yourprovider.com -all". A domain that sends no mail should publish "v=spf1 -all".
- RFC 7208
- NIS2 21(2)(e)
- IR 2024/2690 6.7.2(k): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(k): Network security
- NIST SP 800-177r1
- High
No DMARC record found
There is no DMARC record at _dmarc.iloader.org, so receivers have no instruction for mail that fails SPF and DKIM.
What to do: Publish a TXT record at _dmarc.iloader.org, starting with "v=DMARC1; p=none; rua=mailto:dmarc@iloader.org" and moving to p=quarantine or p=reject once reports look clean.
- CAPEC-98
- RFC 9989
- NIS2 21(2)(e)
- IR 2024/2690 6.7.2(k): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(k): Network security
- NIST SP 800-177r1
- High
Need hands-on remediation? Email guard@offseq.com
Keep watching iloader.org
This scan found 11 issues across 5 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.
Daily monitoring
Recommended€25per month
- TLS certificates and expiry
- DNS records
- SPF, DKIM and DMARC
- Security headers
- GDPR and NIS2 posture
- Exposed services
- Third-party trackers
- Security score drift
Email alerts on material changes and an exportable JSON history of every change.
Billed monthly. Cancel anytime. The full timeline opens with your unlock code.
Full report
€39.90one-time
- The complete analysis as a PDF you can cite
- Email delivery with an unlock code
- Lifetime access to this report
Prices incl. 21% VAT. Payments by EveryPay; sold by SEQ SIA, Latvia.
Results by check
Each check with its score, findings and the evidence it collected.
How this score is calculated
The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.
Counted in this score
- SSL/TLS
- 89
- Security headers
- 68
- Email security
- 65
- DNS health
- 95
- Network security
- 100
- Website hygiene
- 95
- GDPR outside view
- 100
- Average
- 87
Not counted
- NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
- OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.
- Accessibility: Accessibility is a separate readout from security, so it is reported but not scored. Shown on its own.
Findings that cap the score at 49
Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.
- The certificate is not trusted by browsers
- The website is not served over HTTPS
- A database, remote desktop, file-sharing or Telnet service is reachable from the internet
- The page loads a script from a compromised source
- The domain registration has expired
- SPF authorises every server to send mail as the domain
Partial scans
When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.
Risk levels
- Critical0–25
- High26–49
- Medium50–75
- Low76–100
Technical appendix
Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.
Business context
Business profile
Security posture
Recommendations
- Implement a visible cookie consent banner to comply with EU and global privacy regulations.
- Publish a dedicated security policy and incident response plan accessible from the website footer.
- Add a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
- Enhance contact options with a dedicated security or abuse email address.
- Regularly audit and update third-party dependencies and monitor for emerging security threats.
Site observations
Automated reading of the public site. Ratings are indicative.
Business
- Company
- iloader
- Description
- iloader is an independent IPA app library for iPhone and iPad users who use sideloading tools. The site offers app discovery, release information, compatibility notes, installation guidance, and approved IPA file delivery during a paid access period.
- Key services
- IPA app discovery, Version and compatibility comparison, Individual IPA file delivery, Installation guidance, Access management via purchase accounts
- Content quality
- excellent
- Branding
- consistent
Technology
- Stack
- React, Next.js, Supabase, Dodo Payments, Resend
- Frameworks
- Next.js, React
- Platforms
- Web
- Performance
- fast
- Mobile
- excellent
- Accessibility
- good
- SEO
- good
Security
- Observed score
- 90/100
- Good practices seen
- HTTPS enforced
- No exposed sensitive data in HTML
- Secure forms with minimal data collection
- No third-party trackers or ads detected
Analytics and tracking
- Tracking level
- minimal
- Privacy practices
- excellent
Advertising
- Transparency
- excellent
Site quality
- Design
- excellent
- User experience
- excellent
- Content relevance
- excellent
- Navigation
- excellent
- Professionalism
- excellent
- Trustworthiness
- high
Key observations
- Website is fully accessible with no blocking or WAF challenges
- Content is well-structured, professional, and focused on IPA app library services
- No direct contact emails or phone numbers found; contact is via web form
- No cookie consent mechanism detected despite privacy policy presence
- No advertising or tracking scripts detected, indicating privacy-conscious design
- Use of modern web technologies and frameworks
- Clear separation of library access and installation tools
- No evidence of malware or phishing
- No explicit security policy or incident response information published
Technical notes
Notes
Standards and sources
Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.
- MITRE CWE (opens in a new tab)4.20 (2026-04-30) · CWE Terms of Use (free use with attribution, © MITRE)
- OWASP Top 10:2025 (opens in a new tab)2025 (membership per CWE 4.20) · CC BY-SA 4.0
- MITRE CAPEC (opens in a new tab)3.9 (2023-01-24) · CAPEC Terms of Use (free use with attribution, © MITRE)
- OWASP ASVS (opens in a new tab)5.0.0 · CC BY-SA 4.0
- OWASP Web Security Testing Guide (opens in a new tab)latest (checklist.json, master) · CC BY-SA 4.0
- OWASP Secure Headers Project (opens in a new tab)2026-10-18 · Apache-2.0
- Mozilla Server Side TLS (intermediate) (opens in a new tab)6.0 · MPL-2.0
- NIST SP 800-53 Rev. 5 (OSCAL catalog) (opens in a new tab)5.2.0 · Public domain (US Government work)
- Directive (EU) 2022/2555 (NIS2) (opens in a new tab)OJ L 333, 27.12.2022 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Commission Implementing Regulation (EU) 2024/2690 (opens in a new tab)OJ L, 18.10.2024 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Regulation (EU) 2016/679 (GDPR) (opens in a new tab)OJ L 119, 4.5.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Directive 2002/58/EC (ePrivacy), consolidated (opens in a new tab)19.12.2009 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- RFC Editor metadata (opens in a new tab)per-RFC (obsolete RFCs rejected) · IETF Trust Legal Provisions (metadata only)
- NIST CSRC, W3C TR, IETF Datatracker, EDPB, EUR-Lex CELLAR and gesetze-bayern.de (opens in a new tab)per document · Titles and links only
- NIST NVD CVE API 2.0 (opens in a new tab)live records · Public domain (NVD); CVE® records © MITRE, free use
- W3C WCAG 2.2 (opens in a new tab)W3C Recommendation (wcag.json) · W3C Software and Document License
- ETSI EN 301 549 (opens in a new tab)V3.2.1 (2021-03), clause headings · Clause numbers and titles only (© ETSI)
- Directive (EU) 2019/882 (European Accessibility Act) (opens in a new tab)OJ L 151, 7.6.2019 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Directive (EU) 2016/2102 (Web Accessibility Directive) (opens in a new tab)OJ L 327, 2.12.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
Retrieved 2026-10-25
Feedback on this report
Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.
Reviews of this site
Share your experience with iloader.org. Every review is verified by email and published after moderation.
Community rating
Loading reviews…