Domain

next.sc

Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.

DNS Check HTTP Check Run Full Scan .sc TLD

Run a live full scan of next.sc

On-demand: ports, banners, TLS, tech-stack, subdomains and origin/IP-leak detection. Results are shared publicly for everyone to link to.

Deep-scan now

Hosting IPs

172

A/AAAA targets

Subdomains

234

CT + scan + body

Record Types

—

seen in DNS

Observed Certs

—

in our scans

DNS Records

—

AAAA

—

TXT

—

CNAME

—

CAA

—

WHOIS / Registration

Registration data planned

Registrar, creation/expiry dates and domain status via RDAP. Rolling out gradually — bulk WHOIS is rate-limited, so we resolve on a prioritized cadence.

Subdomains

Every subdomain we know about — harvested from CT-log SANs, scan-observed certs and HTML body references — paired with its current A/AAAA target.

Subdomain	Resolves to	Last seen
common-media.staging.eu.next.sc	13.226.244.30 2600:9000:2449:d000:0:1f7f:8500:93a1 2600:9000:2449:4c00:0:1f7f:8500:93a1 2600:9000:2013:ea00:0:1f7f:8500:93a1 +20	2026-06-02 21:29:33.934
common-media.staging.us.next.sc	54.192.35.107 2600:9000:238d:b600:16:71a3:7840:93a1 2600:9000:238d:2800:16:71a3:7840:93a1 2600:9000:20b4:cc00:16:71a3:7840:93a1 +16	2026-06-02 22:24:14.147
common-media.edge.eu.next.sc	65.8.131.88 2600:9000:20b4:ea00:2:e5e9:8140:93a1 2600:9000:20b4:bc00:2:e5e9:8140:93a1 2600:9000:20b4:ae00:2:e5e9:8140:93a1 +8	2026-06-02 20:05:38.334
scos-ota-test.screens.staging.next.sc	3.161.82.99 2600:9000:26e8:3600:d:d55f:11c0:93a1 2600:9000:26e8:9c00:d:d55f:11c0:93a1 2600:9000:26e8:f200:d:d55f:11c0:93a1 +8	2026-06-21 11:42:16.222
api.marketing.staging.next.sc	65.8.131.79 18.239.69.3 18.239.69.23 18.239.69.80 +4	2026-06-05 22:15:51.442
ui.next.sc	185.199.109.153 185.199.110.153 185.199.111.153 185.199.108.153 +4	2026-06-18 02:46:59.133
billing-backend.staging.eu.next.sc	52.209.229.247 34.248.231.81 52.212.73.141 52.208.8.134 +2	2026-07-16 11:41:13.397
ws.eu.staging.next.sc	52.48.49.73 54.194.217.252 54.74.201.196 99.81.255.140 +2	2026-06-17 02:20:48.081
auth.edge.next.sc	3.173.161.67 3.173.161.98 3.173.161.73 3.173.161.34	2026-07-17 00:44:27.458
mc.staging.eu.next.sc	13.226.244.97 13.226.244.128 13.226.244.24 13.226.244.79	2026-06-17 14:03:20.277
player.edge.eu.next.sc	143.204.181.47 143.204.181.29 143.204.181.37 143.204.181.13	2026-06-19 22:41:02.826
player.screens.staging.next.sc	18.239.105.40 18.239.105.10 18.239.105.119 18.239.105.8	2026-06-15 15:34:27.930
player.staging.us.next.sc	18.239.50.54 18.239.50.55 18.239.50.129 18.239.50.107	2026-07-16 22:48:30.844
proving-ground.sites.staging.us.next.sc	18.238.243.17 18.238.243.9 18.238.243.92 18.238.243.82	2026-06-17 14:03:20.277
studio-preview-staging-pr-13158.staging.next.sc	3.173.161.10 3.173.161.34 3.173.161.60 3.173.161.71	2026-06-16 21:27:43.355
studio-preview-staging-pr-13166.staging.next.sc	18.245.46.90 18.245.46.113 18.245.46.52 18.245.46.69	2026-06-18 18:47:39.441
testlab-console.staging.next.sc	3.173.161.92 3.173.161.77 3.173.161.25 3.173.161.48	2026-07-16 17:51:31.792
timezone.edge.next.sc	18.239.50.5 18.239.50.69 18.239.50.92 18.239.50.60	2026-07-16 08:59:42.295
webclient.edge.eu.next.sc	3.173.161.17 3.173.161.80 3.173.161.33 3.173.161.29	2026-06-15 03:11:14.776
webclient.staging.eu.next.sc	18.239.83.126 18.239.83.67 18.239.83.106 18.239.83.123	2026-06-17 08:13:25.551
billing-backend.staging.euw1.next.sc	34.248.231.81 54.74.89.213 63.35.157.213	2026-06-03 10:58:03.757
link-validation.staging.us.next.sc	3.129.56.39 18.225.127.173 3.13.249.86	2026-07-17 02:42:55.040
link-validation.staging.use2.next.sc	3.129.56.39 18.225.127.173 3.13.249.86	2026-07-17 02:42:55.040
loki.edge.next.sc	52.19.20.122 54.171.71.188 52.31.198.97	2026-05-27 07:31:38.646
player-logs-grafana-service.staging.eu.next.sc	52.208.8.134 52.209.229.247 52.212.73.141	2026-07-15 23:54:29.904
player-logs-grafana-service.staging.euw1.next.sc	52.209.229.247 52.208.8.134 52.212.73.141	2026-07-15 23:54:29.904
pulse-backend-aws.staging.eu.next.sc	54.228.207.67 34.253.95.227 54.78.183.141	2026-05-26 08:19:24.378
ws.us.staging.next.sc	18.227.23.148 3.21.85.47 18.116.145.62	2026-06-17 02:20:48.081
api.us.staging.next.sc	3.136.63.23 3.151.1.111	2026-06-14 23:37:38.836
app.staging.next.sc	216.150.16.65 216.150.1.65	2026-07-17 05:27:09.693
graphql.staging.us.next.sc	3.139.244.183 3.15.109.158	2026-07-17 02:42:55.040
graphql.staging.use2.next.sc	3.139.244.183 3.15.109.158	2026-07-17 02:42:55.040
rdm.edge.next.sc	66.33.60.194 76.76.21.93	2026-06-24 00:12:22.073
rdm.staging.next.sc	76.76.21.123 66.33.60.35	2026-06-21 23:04:07.065
studio-webhooks.staging.us.next.sc	3.147.223.127 3.136.66.135	2026-06-21 09:20:50.583
telemetry.edge.next.sc	52.49.105.131 34.245.255.102	2026-06-19 04:29:30.037
amc.staging.next.sc		1970-01-01 00:00:00.000
api.log.staging.eu.next.sc		1970-01-01 00:00:00.000
api.log.staging.euc1.next.sc		1970-01-01 00:00:00.000
api.log.staging.euw1.next.sc		1970-01-01 00:00:00.000
api.log.staging.us.next.sc		1970-01-01 00:00:00.000
api.log.staging.use2.next.sc		1970-01-01 00:00:00.000
api.log.staging.usw2.next.sc		1970-01-01 00:00:00.000
api.renderer.staging.eu.next.sc		1970-01-01 00:00:00.000
api.renderer.staging.euw1.next.sc		1970-01-01 00:00:00.000
api.renderer.staging.us.next.sc		1970-01-01 00:00:00.000
api.renderer.staging.use2.next.sc		1970-01-01 00:00:00.000
api.signal.staging.euw1.next.sc		1970-01-01 00:00:00.000
api.signal.staging.next.sc		1970-01-01 00:00:00.000
api.sites.edge.eu.next.sc		1970-01-01 00:00:00.000
api.sites.edge.euw1.next.sc		1970-01-01 00:00:00.000
api.sites.staging.eu.next.sc		1970-01-01 00:00:00.000
api.sites.staging.euc1.next.sc		1970-01-01 00:00:00.000
api.sites.staging.euw1.next.sc		1970-01-01 00:00:00.000
authenticate.next.sc		1970-01-01 00:00:00.000
billing-backend.staging.euc1.next.sc	52.58.155.244	2026-07-16 11:41:13.397
billing-backend.staging.us.next.sc		1970-01-01 00:00:00.000
billing-backend.staging.usw2.next.sc		1970-01-01 00:00:00.000
billing-service.staging.eu.next.sc		1970-01-01 00:00:00.000
billing-service.staging.euc1.next.sc		1970-01-01 00:00:00.000
billing-service.staging.us.next.sc		1970-01-01 00:00:00.000
billing-service.staging.use2.next.sc		1970-01-01 00:00:00.000
canary.staging.eu.next.sc		1970-01-01 00:00:00.000
default.data.staging.eu.next.sc		1970-01-01 00:00:00.000
default.edge.eu.next.sc		1970-01-01 00:00:00.000
default.staging.eu.next.sc		1970-01-01 00:00:00.000
default.staging.next.sc		1970-01-01 00:00:00.000
edge.eu.next.sc		1970-01-01 00:00:00.000
edge.next.sc		1970-01-01 00:00:00.000
embed.edge.next.sc		1970-01-01 00:00:00.000
embed.staging.next.sc		1970-01-01 00:00:00.000
file-processing.edge.euw1.next.sc		1970-01-01 00:00:00.000
file-processing.staging.euc1.next.sc		1970-01-01 00:00:00.000
file-processing.staging.use2.next.sc		1970-01-01 00:00:00.000
graphql.staging.eu.next.sc		1970-01-01 00:00:00.000
graphql.staging.euw1.next.sc		1970-01-01 00:00:00.000
graphql.staging.usw2.next.sc		1970-01-01 00:00:00.000
id.staging.euc1.next.sc		1970-01-01 00:00:00.000
id.staging.next.sc		1970-01-01 00:00:00.000
identity.staging.eu.next.sc		1970-01-01 00:00:00.000
identity.staging.euc1.next.sc		1970-01-01 00:00:00.000
identity.staging.us.next.sc		1970-01-01 00:00:00.000
identity.staging.use2.next.sc		1970-01-01 00:00:00.000
link-validation-v2.edge.eu.next.sc		1970-01-01 00:00:00.000
link-validation-v2.staging.eu.next.sc		1970-01-01 00:00:00.000
link-validation-v2.staging.us.next.sc		1970-01-01 00:00:00.000
link-validation.staging.eu.next.sc		1970-01-01 00:00:00.000
link-validation.staging.euc1.next.sc		1970-01-01 00:00:00.000
location.edge.next.sc		1970-01-01 00:00:00.000
logs.staging.eu.next.sc		1970-01-01 00:00:00.000
logs.staging.euc1.next.sc		1970-01-01 00:00:00.000
logs.staging.us.next.sc		1970-01-01 00:00:00.000
logs.staging.use2.next.sc		1970-01-01 00:00:00.000
marketing-event-service.edge.eu.next.sc		1970-01-01 00:00:00.000
marketing-event-service.edge.euw1.next.sc		1970-01-01 00:00:00.000
marketing-event-service.staging.eu.next.sc		1970-01-01 00:00:00.000
marketing-event-service.staging.euw1.next.sc		1970-01-01 00:00:00.000
marketing-event-service.staging.us.next.sc		1970-01-01 00:00:00.000
marketing-event-service.staging.use2.next.sc		1970-01-01 00:00:00.000
marketing-event-service.staging.usw2.next.sc		1970-01-01 00:00:00.000
mc.edge.eu.next.sc		1970-01-01 00:00:00.000
media-resizing.edge.eu.next.sc		1970-01-01 00:00:00.000
media-resizing.edge.euw1.next.sc		1970-01-01 00:00:00.000
media-resizing.staging.eu.next.sc		1970-01-01 00:00:00.000
media-resizing.staging.euc1.next.sc		1970-01-01 00:00:00.000
media-resizing.staging.euw1.next.sc		1970-01-01 00:00:00.000
media-resizing.staging.us.next.sc		1970-01-01 00:00:00.000
media-resizing.staging.use2.next.sc		1970-01-01 00:00:00.000
media-resizing.staging.usw2.next.sc		1970-01-01 00:00:00.000
media.edge.eu.next.sc		1970-01-01 00:00:00.000
media.staging.eu.next.sc		1970-01-01 00:00:00.000
media.staging.us.next.sc		1970-01-01 00:00:00.000
migrate.staging.next.sc		1970-01-01 00:00:00.000
player-logs-grafana-service.staging.euc1.next.sc	35.159.45.4	2026-07-15 23:54:29.904
player.screens.edge.next.sc		1970-01-01 00:00:00.000
player.staging.eu.next.sc		1970-01-01 00:00:00.000
pulse-frontend.staging.eu.next.sc		1970-01-01 00:00:00.000
screens.staging.next.sc		1970-01-01 00:00:00.000
secure-media-resize.edge.eu.next.sc		1970-01-01 00:00:00.000
secure-media-resize.staging.eu.next.sc		1970-01-01 00:00:00.000

Tech Stack

Tech detection pending

Wappalyzer-rules detect CMS, frameworks, analytics, JS libs and server-side languages on this domain.

TLS Certificates

Certificate observations pending

TLS certs naming this domain in subject or SANs will appear here as our scan-layer catches them.

IPs Citing This Domain

No citing IPs found yet

As the world-sweep progresses, hosts referencing this domain in their HTML will surface here.

Origin / IP-Leak

USP

When a hostname is served behind a CDN (e.g. Cloudflare), the origin server can sometimes be identified by matching its TLS cert against the protected hostname. Findings shown here are heuristic candidates, not guarantees.

No origin-IP leaks detected (yet)

Either this domain doesn't sit behind a CDN, or we haven't seen a TLS cert from a non-CDN IP matching this hostname. Run a fullscan to refresh the cert→IP cross-reference.

Threat Intelligence

Domain threat-intel pending

Matches in URLhaus, OpenPhish, PhishTank, malware feeds, and Spamhaus DBL.

History

Domain timeline pending

Passive-DNS history accumulates as our forward-DNS crawler observes A/AAAA/MX/NS/TXT records over time.