Domain
coreserver.jp
Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.
Run a live full scan of coreserver.jp
On-demand: ports, banners, TLS, tech-stack, subdomains and origin/IP-leak detection. Results are shared publicly for everyone to link to.
Hosting IPs
—
A/AAAA targets
Subdomains
—
CT + scan + body
Record Types
—
seen in DNS
Observed Certs
—
in our scans
DNS Records
A
104.18.24.150, 104.18.25.150
AAAA
—
MX
10 mail.coreserver.jp
NS
gabriel.ns.cloudflare.com, vera.ns.cloudflare.com
TXT
_globalsign-domain-verification=rgM5jLvewIPQ1kUWl4oyGT2IX6lJq_GqQv8kTD5OAY, google-site-verification=M52iG-enU0nhGjZ1Rv0-Jd8Gpn3NEjwa4cWvyYct9tU, v=spf1 a:www.coreserver.jp ip4:202.172.25.31 include:_spf.google.com ~all, v=spf1 redirect=value-domain.com
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
Subdomain enumeration pending
Every subdomain ever issued a TLS cert under this apex — extracted from Certificate Transparency logs, our own scan observations and body references.
Tech Stack
Tech detection pending
Wappalyzer-rules detect CMS, frameworks, analytics, JS libs and server-side languages on this domain.
TLS Certificates
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
Subject: v2003.coreserver.jp
Issuer: v2003.coreserver.jp
SANs: v2003.coreserver.jp
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
Subject: v2002.coreserver.jp
Issuer: v2002.coreserver.jp
SANs: v2002.coreserver.jp
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
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.
| Origin IP | Origin ASN | CDN ASN | Confidence | Reasoning |
|---|---|---|---|---|
| 160.251.152.101 | AS58791 | AS13335 | 95% | cert 164bf741… served by 160.251.152.101 (AS58791) carries SAN coreserver.jp which currently resolves through Cloudflare (AS13335) at 104.18.24.150, 104.18.25.150 |
| 202.172.26.28 | AS37907 | AS13335 | 95% | cert 164bf741… served by 202.172.26.28 (AS37907) carries SAN coreserver.jp which currently resolves through Cloudflare (AS13335) at 104.18.24.150, 104.18.25.150 |
| 202.172.26.17 | AS37907 | AS13335 | 95% | cert 164bf741… served by 202.172.26.17 (AS37907) carries SAN coreserver.jp which currently resolves through Cloudflare (AS13335) at 104.18.24.150, 104.18.25.150 |
| 202.172.26.44 | AS37907 | AS13335 | 95% | cert 164bf741… served by 202.172.26.44 (AS37907) carries SAN coreserver.jp which currently resolves through Cloudflare (AS13335) at 104.18.24.150, 104.18.25.150 |
| 202.172.28.103 | AS37907 | AS13335 | 95% | cert 164bf741… served by 202.172.28.103 (AS37907) carries SAN coreserver.jp which currently resolves through Cloudflare (AS13335) at 104.18.24.150, 104.18.25.150 |
| 202.172.26.20 | AS37907 | AS13335 | 95% | cert 164bf741… served by 202.172.26.20 (AS37907) carries SAN coreserver.jp which currently resolves through Cloudflare (AS13335) at 104.18.24.150, 104.18.25.150 |
| 202.172.25.52 | AS37907 | AS13335 | 95% | cert 164bf741… served by 202.172.25.52 (AS37907) carries SAN coreserver.jp which currently resolves through Cloudflare (AS13335) at 104.18.24.150, 104.18.25.150 |
| 202.172.28.76 | AS37907 | AS13335 | 95% | cert 164bf741… served by 202.172.28.76 (AS37907) carries SAN coreserver.jp which currently resolves through Cloudflare (AS13335) at 104.18.24.150, 104.18.25.150 |
| 202.172.28.129 | AS37907 | AS13335 | 95% | cert 164bf741… served by 202.172.28.129 (AS37907) carries SAN coreserver.jp which currently resolves through Cloudflare (AS13335) at 104.18.24.150, 104.18.25.150 |
| 202.172.28.171 | AS37907 | AS13335 | 95% | cert 164bf741… served by 202.172.28.171 (AS37907) carries SAN coreserver.jp which currently resolves through Cloudflare (AS13335) at 104.18.24.150, 104.18.25.150 |
| 202.172.28.174 | AS37907 | AS13335 | 95% | cert 164bf741… served by 202.172.28.174 (AS37907) carries SAN coreserver.jp which currently resolves through Cloudflare (AS13335) at 104.18.24.150, 104.18.25.150 |
| 202.172.28.62 | AS37907 | AS13335 | 95% | cert 164bf741… served by 202.172.28.62 (AS37907) carries SAN coreserver.jp which currently resolves through Cloudflare (AS13335) at 104.18.24.150, 104.18.25.150 |
| 202.172.26.12 | AS37907 | AS13335 | 95% | cert 164bf741… served by 202.172.26.12 (AS37907) carries SAN coreserver.jp which currently resolves through Cloudflare (AS13335) at 104.18.24.150, 104.18.25.150 |
| 202.172.28.31 | AS37907 | AS13335 | 95% | cert 164bf741… served by 202.172.28.31 (AS37907) carries SAN coreserver.jp which currently resolves through Cloudflare (AS13335) at 104.18.24.150, 104.18.25.150 |
| 202.172.26.8 | AS37907 | AS13335 | 95% | cert 164bf741… served by 202.172.26.8 (AS37907) carries SAN coreserver.jp which currently resolves through Cloudflare (AS13335) at 104.18.24.150, 104.18.25.150 |
| 202.172.28.185 | AS37907 | AS13335 | 95% | cert 164bf741… served by 202.172.28.185 (AS37907) carries SAN coreserver.jp which currently resolves through Cloudflare (AS13335) at 104.18.24.150, 104.18.25.150 |
| 202.172.26.2 | AS37907 | AS13335 | 95% | cert 164bf741… served by 202.172.26.2 (AS37907) carries SAN coreserver.jp which currently resolves through Cloudflare (AS13335) at 104.18.24.150, 104.18.25.150 |
| 160.251.152.104 | AS58791 | AS13335 | 95% | cert 164bf741… served by 160.251.152.104 (AS58791) carries SAN coreserver.jp which currently resolves through Cloudflare (AS13335) at 104.18.24.150, 104.18.25.150 |
| 202.172.28.130 | AS37907 | AS13335 | 95% | cert 164bf741… served by 202.172.28.130 (AS37907) carries SAN coreserver.jp which currently resolves through Cloudflare (AS13335) at 104.18.24.150, 104.18.25.150 |
| 202.172.28.151 | AS37907 | AS13335 | 95% | cert 164bf741… served by 202.172.28.151 (AS37907) carries SAN coreserver.jp which currently resolves through Cloudflare (AS13335) at 104.18.24.150, 104.18.25.150 |
| 202.172.28.82 | AS37907 | AS13335 | 95% | cert 164bf741… served by 202.172.28.82 (AS37907) carries SAN coreserver.jp which currently resolves through Cloudflare (AS13335) at 104.18.24.150, 104.18.25.150 |
| 202.172.28.193 | AS37907 | AS13335 | 95% | cert 164bf741… served by 202.172.28.193 (AS37907) carries SAN coreserver.jp which currently resolves through Cloudflare (AS13335) at 104.18.24.150, 104.18.25.150 |
| 202.172.26.9 | AS37907 | AS13335 | 95% | cert 164bf741… served by 202.172.26.9 (AS37907) carries SAN coreserver.jp which currently resolves through Cloudflare (AS13335) at 104.18.24.150, 104.18.25.150 |
| 202.172.28.20 | AS37907 | AS13335 | 95% | cert 164bf741… served by 202.172.28.20 (AS37907) carries SAN coreserver.jp which currently resolves through Cloudflare (AS13335) at 104.18.24.150, 104.18.25.150 |
| 202.172.28.112 | AS37907 | AS13335 | 95% | cert 164bf741… served by 202.172.28.112 (AS37907) carries SAN coreserver.jp which currently resolves through Cloudflare (AS13335) at 104.18.24.150, 104.18.25.150 |
CT-Log Evidence
Certificates from public Certificate Transparency logs whose subject or SAN names this domain — including historic certs we never observed live.
1c00cf33bb19440f…
sectigo · elephant2026h1
Subject: coreserver.jp
Issuer: Sectigo Public Server Authentication CA DV R36
SANs: coreserver.jp, *.coreserver.jp
Valid: 2026-01-15 00:00:00 → 2026-04-15 23:21:28
3693c1d07fd90b88…
sectigo · elephant2026h1
Subject: coreserver.jp
Issuer: Sectigo Public Server Authentication CA DV E36
SANs: coreserver.jp, *.coreserver.jp
Valid: 2026-01-15 00:00:00 → 2026-04-15 23:35:40
44f7eb1524a9fbdc…
sectigo · elephant2026h1
Subject: coreserver.jp
Issuer: Sectigo Public Server Authentication CA DV R36
SANs: coreserver.jp, *.coreserver.jp
Valid: 2026-01-15 00:00:00 → 2026-04-15 23:21:28
8df9ab5d2ea01607…
sectigo · elephant2026h1
Subject: coreserver.jp
Issuer: Sectigo Public Server Authentication CA DV E36
SANs: coreserver.jp, *.coreserver.jp
Valid: 2026-01-15 00:00:00 → 2026-04-15 23:35:40
2516a0cab457cbdf…
sectigo · elephant2026h1
Subject: coreserver.jp
Issuer: WR1
SANs: coreserver.jp, *.coreserver.jp
Valid: 2025-11-29 06:49:45 → 2026-02-27 07:47:17
2eb8797362f2467c…
sectigo · elephant2026h1
Subject: coreserver.jp
Issuer: Sectigo Public Server Authentication CA DV R36
SANs: coreserver.jp, *.coreserver.jp
Valid: 2025-11-18 00:00:00 → 2026-02-15 21:45:03
8e880624e23b7a74…
sectigo · elephant2026h1
Subject: coreserver.jp
Issuer: Sectigo Public Server Authentication CA DV E36
SANs: coreserver.jp, *.coreserver.jp
Valid: 2025-11-18 00:00:00 → 2026-02-16 07:55:41
90d86bbe165601a4…
sectigo · elephant2026h1
Subject: coreserver.jp
Issuer: Sectigo Public Server Authentication CA DV E36
SANs: coreserver.jp, *.coreserver.jp
Valid: 2025-11-18 00:00:00 → 2026-02-16 07:55:41
e86bc69603e05c3b…
sectigo · elephant2026h1
Subject: coreserver.jp
Issuer: Sectigo Public Server Authentication CA DV R36
SANs: coreserver.jp, *.coreserver.jp
Valid: 2025-11-18 00:00:00 → 2026-02-15 21:45:03
524afbf6cbe59ab8…
google · argon2026h1
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
Valid: 2025-05-16 02:26:56 → 2026-06-17 02:26:55
06b6d14d7fea2215…
google · argon2026h1
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
Valid: 2025-05-16 02:26:56 → 2026-06-17 02:26:55
06b6d14d7fea2215…
google · xenon2026h1
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
Valid: 2025-05-16 02:26:56 → 2026-06-17 02:26:55
524afbf6cbe59ab8…
google · xenon2026h1
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
Valid: 2025-05-16 02:26:56 → 2026-06-17 02:26:55
524afbf6cbe59ab8…
sectigo · elephant2026h1
Subject: *.coreserver.jp
Issuer: GlobalSign GCC R3 DV TLS CA 2020
SANs: *.coreserver.jp, coreserver.jp
Valid: 2025-05-16 02:26:56 → 2026-06-17 02:26:55
Threat Intelligence
Domain threat-intel pending
Matches in URLhaus, OpenPhish, PhishTank, malware feeds, and Spamhaus DBL.
History
Passive DNS — every value this name ever resolved to and when we first / last observed it. Updates every cycle of our forward-DNS crawler.
| Type | Value | First seen | Last seen |
|---|---|---|---|
| A | 104.18.25.150 | 2026-05-25 21:30:03.372 | 2026-07-24 23:33:45.118 |
| A | 104.18.24.150 | 2026-05-25 21:30:03.372 | 2026-07-24 23:33:45.118 |
| MX | 10 mail.coreserver.jp | 2026-05-26 02:34:00.508 | 2026-07-24 23:33:45.118 |
| TXT | v=spf1 a:www.coreserver.jp ip4:202.172.25.31 include:_spf.google.com ~all | 2026-05-26 02:34:00.508 | 2026-07-24 23:33:45.118 |
| NS | vera.ns.cloudflare.com | 2026-05-26 02:34:00.508 | 2026-07-24 23:33:45.118 |
| TXT | v=spf1 redirect=value-domain.com | 2026-05-26 02:34:00.508 | 2026-07-24 23:33:45.118 |
| NS | gabriel.ns.cloudflare.com | 2026-05-26 02:34:00.508 | 2026-07-24 23:33:45.118 |
| TXT | google-site-verification=M52iG-enU0nhGjZ1Rv0-Jd8Gpn3NEjwa4cWvyYct9tU | 2026-05-26 02:34:00.508 | 2026-07-24 23:33:45.118 |
| TXT | _globalsign-domain-verification=rgM5jLvewIPQ1kUWl4oyGT2IX6lJq_GqQv8kTD5OAY | 2026-06-14 22:08:58.337 | 2026-07-24 23:33:45.118 |