Domain

apem.com

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

DNS Check HTTP Check Run Full Scan .com TLD

Run a live full scan of apem.com

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

A/AAAA targets

Subdomains

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
apem.com	104.110.240.129 2a02:26f0:e600::170f:b2f3 2a02:26f0:1700:11::b856:678f 2a02:26f0:1700:11::b856:678b +36	2026-06-17 19:45:48.868
www.apem.com	184.86.103.200 184.86.103.205 2.19.96.202 2.19.96.139 +2	2026-06-23 02:29:43.031
mktg.apem.com	199.60.103.226 199.60.103.30 2606:2c40::c73c:67e2 2606:2c40::c73c:671e	2026-07-21 22:39:47.486
booking.apem.com		1970-01-01 00:00:00.000
dkvpn.apem.com	80.80.15.118	2026-06-18 21:57:42.399
frvpn.apem.com	185.182.255.124	2026-07-24 09:50:09.036
sevpn.apem.com	80.169.180.166	2026-07-22 18:48:05.462
tnvpn.apem.com	41.224.0.225	2026-07-27 09:00:22.844
ukvpn.apem.com	212.36.185.182	2026-06-22 04:48:04.025

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.

CT-Log Evidence

Certificates from public Certificate Transparency logs whose subject or SAN names this domain — including historic certs we never observed live.

518c2fe0e5abd39a… google · argon2026h2

Subject: idec.com

Issuer: DigiCert Global G3 TLS ECC SHA384 2020 CA1