Check-Host.cc

Domain

sidersa.com

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

Run a live full scan of sidersa.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
74.208.165.109
AAAA
MX
1 aspmx.l.google.com, 10 alt3.aspmx.l.google.com, 10 alt4.aspmx.l.google.com, 5 alt1.aspmx.l.google.com, 5 alt2.aspmx.l.google.com
NS
ns1050.ui-dns.com, ns1054.ui-dns.biz, ns1068.ui-dns.de, ns1115.ui-dns.org
TXT
v=DMARC1; p=none; rua=mailto:dmarc@sidersa.com; ruf=mailto:dmarc@sidersa.com; fo=1;rua=mailto:dmarc-reports@sidersa.com, v=spf1 mx ip4:200.68.95.89 ip4:200.61.186.192/28 a:mailserver.sidersa.com include:_spf.google.com include:zcsend.net ~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

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: *.sidersa.com
Issuer: Sectigo Public Server Authentication CA DV R36
SANs: *.sidersa.com, sidersa.com
Subject: *.sidersa.com
Issuer: Sectigo Public Server Authentication CA DV R36
SANs: *.sidersa.com, sidersa.com

IPs Citing This Domain

Hosts whose HTML body references this domain. Strong signal for origin/mirror/embed discovery.

74.208.165.109:443 href · ×2

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

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
NS ns1054.ui-dns.biz 2026-05-26 00:21:04.925 2026-07-28 14:28:46.692
TXT v=DMARC1; p=none; rua=mailto:dmarc@sidersa.com; ruf=mailto:dmarc@sidersa.com; fo=1;rua=mailto:dmarc-reports@sidersa.com 2026-05-26 00:21:04.925 2026-05-26 00:21:04.925
NS ns1068.ui-dns.de 2026-05-26 00:21:04.925 2026-07-28 14:28:46.692
NS ns1115.ui-dns.org 2026-05-26 00:21:04.925 2026-07-28 14:28:46.692
TXT v=spf1 mx ip4:200.68.95.89 ip4:200.61.186.192/28 a:mailserver.sidersa.com include:_spf.google.com include:zcsend.net ~all 2026-05-26 00:21:04.925 2026-07-28 14:28:46.692
NS ns1050.ui-dns.com 2026-05-26 00:21:04.925 2026-07-28 14:28:46.692
MX 5 alt2.aspmx.l.google.com 2026-05-26 00:21:04.925 2026-07-28 14:28:46.692
A 74.208.165.109 2026-05-26 00:21:04.925 2026-07-28 14:28:46.692
MX 10 alt4.aspmx.l.google.com 2026-05-26 00:21:04.925 2026-07-28 14:28:46.692
MX 1 aspmx.l.google.com 2026-05-26 00:21:04.925 2026-07-28 14:28:46.692
MX 5 alt1.aspmx.l.google.com 2026-05-26 00:21:04.925 2026-07-28 14:28:46.692
MX 10 alt3.aspmx.l.google.com 2026-05-26 00:21:04.925 2026-07-28 14:28:46.692