Check-Host.cc

Domain

peaksware.com

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

Run a live full scan of peaksware.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
1
A/AAAA targets
Subdomains
3
CT + scan + body
Record Types
4
seen in DNS
Observed Certs
4
in our scans

DNS Records

A
74.114.90.4
AAAA
MX
10 aspmx.l.google.com, 20 alt1.aspmx.l.google.com
NS
ns-1329.awsdns-38.org, ns-1640.awsdns-13.co.uk, ns-204.awsdns-25.com, ns-662.awsdns-18.net
TXT
atlassian-domain-verification=ys/bosZoY30KRUpQ7X8LFiIw3v+VM5aJBVvTeLxtkstKSMQekom9KDWDe0Rm0U6X, google-site-verification=LU0-SqsPbhZ7zIWHGx_4mGINCkh4WYrwvE5HUWVlFlI, miro-verification=84f2d1cfd243e22c77ed3f9f5af3c55abf90e770, openai-domain-verification=dv-EsFCB3uAmXfkuFnMjkyKyxCU, v=spf1 include:_spf.google.com include:mail.zendesk.com include:amazonses.com include:mailsenders.netsuite.com include:spfsalesforce.peaksware.com include:tigertech.net ip4:64.79.155.192 ~all
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
peaksware.com 2026-06-18 14:07:40.853
vpn.peaksware.com
1970-01-01 00:00:00.000
www.peaksware.com 2026-06-18 14:07:40.853

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.