Check-Host.cc

Domain

support.symantec.com

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

Run a live full scan of support.symantec.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
CT + scan + body
Record Types
1
seen in DNS
Observed Certs
7
in our scans

DNS Records

A
141.202.0.1
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

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: casupport.broadcom.com
Issuer: DigiCert Global G2 TLS RSA SHA256 2020 CA1
SANs: casupport.broadcom.com, mysupport.symantec.com, mysymantec.symantec.com, support-prodorigin.broadcom.com, support.ca.com, support.symantec.com, vmwaremigration.broadcom.com
Subject: support.broadcom.com
Issuer: DigiCert Global G2 TLS RSA SHA256 2020 CA1
SANs: assist.broadcom.com, casupport.broadcom.com, enable-sed.broadcom.com, enable.broadcom.com, my.symantec.com, mysupport.symantec.com, mysymantec.symantec.com, partnerportal-prod.broadcom.com, partnerportal.broadcom.com, support-beta.broadcom.com, support-gcpprd.broadcom.com, support-prd.broadcom.com, support-prod.broadcom.com, support.broadcom.com, support.ca.com, support.symantec.com, vmwaremigration.broadcom.com

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

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
A 141.202.0.1 2026-05-26 11:29:02.829 2026-07-24 20:38:03.679