Check-Host.cc

Domain

flyxe.cloud

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

Run a live full scan of flyxe.cloud

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
3
A/AAAA targets
Subdomains
14
CT + scan + body
Record Types
5
seen in DNS
Observed Certs
1
in our scans

DNS Records

A
45.87.246.152
AAAA
MX
0 sv101.ifastnet.com
NS
ns1.flyxe.cloud, ns2.flyxe.cloud
TXT
v=spf1 +mx +a +a:45.87.246.152 +a:94.72.141.210 +a:23.83.223.195 +ip4:82.163.176.145 +ip4:45.87.246.152 +ip4:94.72.141.210 +ip4:23.83.223.195 ~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
api.byid.flyxe.cloud
1970-01-01 00:00:00.000
byid.flyxe.cloud
1970-01-01 00:00:00.000
db1.flyxe.cloud 2026-05-27 00:17:41.200
ddos-protection.flyxe.cloud 2026-07-18 22:07:27.727
flyxe.cloud 2026-06-25 10:23:09.677
moscow.flyxe.cloud
1970-01-01 00:00:00.000
my.flyxe.cloud 2026-05-27 00:17:41.200
server2-alias.flyxe.cloud
1970-01-01 00:00:00.000
server2.flyxe.cloud
1970-01-01 00:00:00.000
www.moscow.flyxe.cloud
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

Subject: api.byid.flyxe.cloud
Issuer: R13
SANs: api.byid.flyxe.cloud
Subject: db1.flyxe.cloud
Issuer: WR1
SANs: *.db1.flyxe.cloud, db1.flyxe.cloud
Subject: flyxe.cloud DDoS-Protection
Issuer: flyxe.cloud DDoS-Protection
SANs:

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.