Check-Host.cc

Domain

upserve.com

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

Run a live full scan of upserve.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

A
AAAA
MX
NS
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
login.upserve.com 2026-06-22 14:08:49.662
status.upserve.com 2026-07-14 21:59:56.300
app.upserve.com 2026-07-25 01:35:31.500
heimdall.upserve.com 2026-06-20 12:01:17.965
click.upserve.com
1970-01-01 00:00:00.000
hello.upserve.com
1970-01-01 00:00:00.000
internal.staging.upserve.com
1970-01-01 00:00:00.000
internal.upserve.com
1970-01-01 00:00:00.000
join.upserve.com
1970-01-01 00:00:00.000
onlineordering.upserve.com 2026-07-20 08:01:27.807
resources.upserve.com 2026-07-20 08:01:27.807
staging.upserve.com
1970-01-01 00:00:00.000
store.upserve.com
1970-01-01 00:00:00.000
upserve.com 2026-07-20 08:01:27.807
www.upserve.com 2026-07-20 08:01:27.807

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.