Skip to main content

Security report for ipify.org

ipify.org · Technology · N/a

Medium risk. 6 critical or high findings in Security headers and GDPR outside view.

Security score

68/100

Risk levelMedium

0–100, higher is better. How it is calculated

ipify.org operates a simple and reliable public IP address API service, primarily targeting developers and IT professionals who need to programmatically obtain their public IPv4 or IPv6 addresses. The service is open source and supported by a robust infrastructure powered by Heroku, ensuring high availability and scalability. The website offers extensive code samples and libraries across many programming languages, facilitating easy integration. The business model is based on providing a free API service with no visitor logging, emphasizing privacy and simplicity. Market position is strong within the niche of IP address APIs, with a reputation for reliability and openness since its founding in 2014. Technically, the website employs modern web technologies including Bootstrap, jQuery, Prism.js, and integrates multiple analytics and marketing tools such as Google Analytics, HubSpot, and CrazyEgg. The site is well-optimized for performance, mobile responsiveness, and accessibility, with a clean and professional design. Hosting infrastructure is implied to be Heroku, contributing to fast and reliable service delivery. However, no CMS or complex frameworks are detected, indicating a lightweight and focused technical stack. From a security perspective, the site enforces HTTPS and avoids collecting sensitive user data, which reduces attack surface. However, it lacks explicit security headers and published security policies such as a privacy policy, cookie policy, or vulnerability disclosure page. The WHOIS data is unavailable or malformed, limiting domain trust verification. Tracking scripts are present without a visible cookie consent mechanism, which may raise privacy compliance concerns. Overall, the security posture is good but could be improved with better transparency and policy publication. The overall risk assessment is moderate with a recommendation to enhance privacy compliance and security transparency. Strategic improvements include publishing privacy and cookie policies, implementing cookie consent, adding security.txt for vulnerability reporting, and improving WHOIS transparency. These steps will strengthen trust and compliance, supporting the service's continued growth and reliability.

Scanned

This is an earlier scan of ipify.org. View the latest report

NIS2 and GDPR posture

GDPR outside view
50/ 100 · Medium
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. 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

6 findings rated critical or high. Fix these first.

  1. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • High

      Missing X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

Need hands-on remediation? Email guard@offseq.com

Keep watching ipify.org

This scan found 21 issues across 6 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 to your card. Cancel anytime. See sample alerts.

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. Secure checkout by Mollie; 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
90
Security headers
15
Email security
65
DNS health
85
Network security
100
GDPR outside view
50
Average
68

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.

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

ipify.org holds a niche market position as a free, open source public IP address API provider, serving developers and IT professionals globally. Its competitive advantages include unlimited usage, IPv4 and IPv6 support, high availability via Heroku infrastructure, and a strong open source presence. Revenue streams are not explicit but likely indirect through related services or partnerships. The target customer segment is technical users needing IP address data for cloud provisioning, tunneling, or geolocation. Growth indicators include extensive code samples and multiple language libraries, fostering community adoption. The partnership ecosystem includes geo.ipify.org for geolocation services. Strategic observations highlight the importance of maintaining transparency and compliance to sustain trust and market position.

Security posture

The security maturity level of ipify.org is moderate to good. HTTPS is enforced site-wide, and no sensitive data collection occurs, minimizing risk. However, the absence of key security headers and published security policies indicates room for improvement. The lack of a vulnerability disclosure mechanism and incident response contact reduces readiness for security events. Privacy compliance is weak due to missing privacy and cookie policies and no consent mechanism despite tracking scripts. WHOIS data is unavailable, which may hinder trust and domain legitimacy verification. Overall, the security culture appears functional but would benefit from enhanced transparency, formal policies, and compliance measures to align with GDPR and other regulations.

Recommendations

  1. Publish a comprehensive privacy policy and cookie policy on the website.
  2. Implement a cookie consent mechanism to comply with privacy regulations.
  3. Add security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Create and publish a security.txt file to facilitate vulnerability disclosure and incident reporting.
  5. Improve WHOIS transparency by ensuring accurate and accessible domain registration data.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
ipify.org
Description
ipify API is a simple public IP address API, easy enough to integrate into any application in seconds.
Key services
Public IP address API (IPv4 and IPv6), IP Geolocation API (via related service geo.ipify.org), Open source API libraries for multiple programming languages
Content quality
excellent
Branding
consistent

Technology

Stack
Google Analytics, HubSpot scripts, CrazyEgg tracking, jQuery, Bootstrap 3.3.7, Prism.js
Platforms
Heroku (infrastructure mentioned)
Performance
fast
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No forms collecting sensitive data
  • No visitor logging

Analytics and tracking

Services
Google Analytics, HubSpot Analytics, CrazyEgg
Tracking level
moderate
Privacy practices
poor

Advertising

Ad networks
HubSpot Ads Pixel, CrazyEgg
Tracking pixels
CrazyEgg, HubSpot Analytics
Marketing tools
HubSpot, CrazyEgg
Transparency
basic

Site quality

Design
excellent
User experience
excellent
Content relevance
excellent
Navigation
excellent
Professionalism
excellent
Trustworthiness
high

Key observations

  1. Website provides a simple, reliable public IP address API service.
  2. Content is developer-centric with extensive code samples and libraries.
  3. No privacy or cookie policies explicitly found on the site.
  4. WHOIS data is unavailable or blocked, limiting domain trust verification.
  5. Uses multiple third-party analytics and marketing tools without visible consent mechanism.
  6. No forms collecting personal or sensitive data detected.
  7. No explicit security or incident response policies published.
Technical notes

Notes

The website uses a modern, lightweight technical stack with Bootstrap 3.3.7 for styling, jQuery for DOM manipulation, and Prism.js for code syntax highlighting. It integrates multiple third-party analytics and marketing tools including Google Analytics, HubSpot, and CrazyEgg, which provide user behavior insights but require privacy compliance enhancements. Hosting is implied to be on Heroku, offering scalability and reliability. The site is well-optimized for performance, mobile responsiveness, and accessibility, with clear navigation and professional design. There is no detected CMS, indicating a custom or static site architecture. Technical risks include reliance on third-party scripts without consent mechanisms and missing security headers. Opportunities exist to modernize security practices and improve privacy compliance to reduce technical debt and regulatory risk.
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.

Retrieved 2026-10-25

Earlier scans of this domain

  1. 68/100Medium30 findingsView report
  2. 68/100Medium30 findingsView report
Reviews of this site

Share your experience with ipify.org. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review ipify.org.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.