MyIP.ms Shopify Stores Scraper avatar

MyIP.ms Shopify Stores Scraper

Pricing

Pay per event

Go to Apify Store
MyIP.ms Shopify Stores Scraper

MyIP.ms Shopify Stores Scraper

Extract Shopify-hosted store domains, IP/hosting metadata, traffic rank, popularity, and DNS records from MyIP.ms.

Pricing

Pay per event

Rating

0.0

(0)

Developer

Stas Persiianenko

Stas Persiianenko

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

6 days ago

Last modified

Share

Extract Shopify-hosted store domains from the public MyIP.ms hosting directory. This actor turns the MyIP.ms Shopify, Inc hosted-sites table into clean rows with store domains, IP addresses, hosting metadata, popularity estimates, DNS records, and source links.

Use it when you need a seed list of Shopify and DTC commerce websites for lead generation, market mapping, enrichment, competitor monitoring, or catalog and pricing workflows.

What does MyIP.ms Shopify Stores Scraper do?

This actor reads MyIP.ms hosted-site directory pages and saves structured website records to an Apify dataset. The default input targets the Shopify, Inc owner page at https://myip.ms/browse/sites/1/own/376714.

It extracts the visible table data and the expanded detail row where MyIP.ms publishes extra signals such as daily visitors, reverse DNS, top-level host, DNS records, and record update time.

Who is it for?

  • ๐Ÿงฒ Lead generation teams building Shopify merchant lists.
  • ๐Ÿ›’ Ecommerce agencies looking for Shopify prospects.
  • ๐Ÿ“Š Market intelligence teams mapping DTC brands and commerce infrastructure.
  • ๐Ÿ”Ž Data enrichment teams needing domain, IP, DNS, and hosting context.
  • ๐Ÿค– Automation builders who want a clean seed dataset for follow-up crawlers.

Why use this actor?

MyIP.ms is useful, but its directory is built for manual browsing. This actor converts those pages into exportable JSON, CSV, Excel, or API-ready records. You can plug the results into CRMs, enrichment tools, monitoring pipelines, or another Apify actor.

How the source works

MyIP.ms lists websites by hosting owner and IP metadata. The Shopify, Inc page includes popular hosted domains, their IP addresses, country, traffic rank, popularity estimates, and related DNS information.

Data fields

FieldDescription
domainDomain shown in the MyIP.ms table.
websiteUrlHTTPS website URL built from the domain.
myipMsDetailUrlMyIP.ms detail page for the website.
ipAddressWebsite IP address from the directory row.
ipWhoisUrlMyIP.ms WHOIS link for the IP address.
hostingCompanyHosting company / IP owner.
hostingCountryServer location country.
hostingCityServer city if MyIP.ms shows it.
worldRankMyIP.ms world popularity rank.
dailyVisitorsEstimated visitors per day from the expanded row.
reverseDnsHostReverse DNS host value.
topLevelHostnameTop-level hostname when present.
dnsRecordsDNS record hostnames listed by MyIP.ms.
recordUpdateTimeMyIP.ms record update timestamp.
sourceUrlDirectory page used for the row.
pageNumberPage number attempted by the actor.
rowNumberRow number shown in the MyIP.ms table.
scrapedAtActor extraction timestamp.

How much does it cost to scrape Shopify stores from MyIP.ms?

The actor uses pay-per-event pricing. You pay a small run-start event plus a per-result event for each website record extracted. Apify shows the exact price before you run the actor.

Input

The input is intentionally small:

{
"startUrls": ["https://myip.ms/browse/sites/1/own/376714"],
"maxResults": 20,
"maxPages": 1,
"delayMs": 1000,
"maxRequestRetries": 3
}

Input options

  • startUrls โ€” MyIP.ms hosted-site directory URLs to scrape.
  • maxResults โ€” maximum records to save.
  • maxPages โ€” maximum directory pages to attempt per start URL.
  • delayMs โ€” polite delay between page requests.
  • maxRequestRetries โ€” retry limit for temporary failures.

Output example

{
"domain": "shopify.com",
"websiteUrl": "https://shopify.com",
"myipMsDetailUrl": "https://myip.ms/view/sites/2379/shopify.com",
"ipAddress": "23.227.38.33",
"hostingCompany": "Shopify, Inc",
"hostingCountry": "Canada",
"worldRank": 122,
"dailyVisitors": 2100000,
"reverseDnsHost": "checkout.shopify.com",
"sourceUrl": "https://myip.ms/browse/sites/1/own/376714",
"pageNumber": 1,
"scrapedAt": "2026-05-20T00:00:00.000Z"
}

Step-by-step guide

  1. Open the actor on Apify.
  2. Keep the prefilled Shopify MyIP.ms URL or paste another MyIP.ms directory URL.
  3. Set maxResults to the number of records you need.
  4. Keep maxPages low for a quick test run.
  5. Click Start.
  6. Export the dataset as CSV, Excel, JSON, or access it by API.

Tips for best results

  • Start with 20 results to confirm the dataset shape.
  • Increase maxResults only after a small run succeeds.
  • Keep delayMs at 1000 ms or higher for polite crawling.
  • Use the myipMsDetailUrl field for manual verification.
  • Combine the dataset with store enrichment or website crawling actors.

Pagination note

MyIP.ms may show human-verification pages for some paginated or export endpoints. The actor stops gracefully if that happens and keeps all records already extracted. The default prefill stays on page 1 because it is reliable and inexpensive for first runs.

Integrations

You can connect this actor to:

  • CRM imports for Shopify merchant outreach.
  • Domain enrichment pipelines.
  • Website screenshot or technology-detection actors.
  • Pricing and catalog monitoring workflows.
  • BI dashboards for Shopify market maps.

API usage

Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/myip-ms-shopify-stores-scraper').call({
startUrls: ['https://myip.ms/browse/sites/1/own/376714'],
maxResults: 20,
maxPages: 1
});
console.log(run.defaultDatasetId);

Python

from apify_client import ApifyClient
client = ApifyClient('YOUR_APIFY_TOKEN')
run = client.actor('automation-lab/myip-ms-shopify-stores-scraper').call(run_input={
'startUrls': ['https://myip.ms/browse/sites/1/own/376714'],
'maxResults': 20,
'maxPages': 1,
})
print(run['defaultDatasetId'])

cURL

curl -X POST "https://api.apify.com/v2/acts/automation-lab~myip-ms-shopify-stores-scraper/runs?token=$APIFY_TOKEN" \
-H 'Content-Type: application/json' \
-d '{"startUrls":["https://myip.ms/browse/sites/1/own/376714"],"maxResults":20,"maxPages":1}'

MCP usage

Use this actor from Claude Desktop, Claude Code, or another MCP client through Apify MCP:

https://mcp.apify.com/?tools=automation-lab/myip-ms-shopify-stores-scraper

Claude Code CLI setup:

$claude mcp add apify-myip-shopify "https://mcp.apify.com/?tools=automation-lab/myip-ms-shopify-stores-scraper"

Claude Desktop JSON config:

{
"mcpServers": {
"apify-myip-shopify": {
"url": "https://mcp.apify.com/?tools=automation-lab/myip-ms-shopify-stores-scraper"
}
}
}

Example prompts:

  • "Run the MyIP.ms Shopify Stores Scraper for 20 records and summarize the highest-traffic domains."
  • "Export Shopify-hosted domains with daily visitors above 10,000."
  • "Find DNS hosts repeated across the MyIP.ms Shopify sample."

Legality

This actor extracts publicly available MyIP.ms directory pages. You are responsible for using the output lawfully, respecting MyIP.ms terms, and complying with privacy, outreach, and data-processing rules in your jurisdiction.

FAQ

What is the best first run size?

Use the prefilled 20-record input first. It is enough to validate the columns, costs, and MyIP.ms availability before increasing volume.

Troubleshooting

Why did I get fewer results than requested?

MyIP.ms can interrupt paginated requests with human verification. The actor saves rows already extracted and stops gracefully when that happens.

Why is hostingCity empty?

MyIP.ms often leaves the city column empty for Shopify-hosted records. The actor preserves the field when available.

Can I scrape non-Shopify MyIP.ms pages?

Yes. Paste another MyIP.ms hosted-site directory URL into startUrls. The output fields remain hosting-directory focused.

Changelog

0.1

Initial version for MyIP.ms Shopify hosted-site directory records.

Notes

  • Source pages are public MyIP.ms pages.
  • The actor is HTTP-only and does not use a browser.
  • The default input is designed for a cheap first run.
  • Results include source URLs for auditability.
  • Dataset rows are suitable for CSV and API workflows.

Field quality checklist

  • Domains are lowercased.
  • URLs are absolute.
  • Numeric ranks and visitor counts are parsed as numbers.
  • DNS records are exported as an array.
  • Duplicate domains are skipped across start URLs.

Responsible use

Use the output as a starting dataset, not as a guarantee that every domain is an active Shopify storefront today. Validate high-value targets before outreach or business decisions.

Support

If MyIP.ms changes its table layout or verification behavior, open an issue with a run URL and sample input so the actor can be adjusted.