Is cruzdid.com safe?
Reviews & Trust Report
Cruzdid.com has been online for just over a year and uses a valid SSL certificate, with no malware or harmful content detected. However, its backlink profile is modest and it lacks any social media presence, resulting in a trust score of 60 out of 100. This site appears generally legitimate but merits a careful look before relying on it fully.
Why cruzdid.com scored 60/100
Each check below either confirmed a good signal or raised a concern. Together they roll up into the trust score.
Malware & Phishing Check
No malware or phishing threats detected by Google Safe Browsing.
securitySSL Certificate
Valid SSL certificate issued by Let's Encrypt. Expires 2026-12-16 (62 days remaining).
securityHTTPS Redirect
HTTP requests are properly redirected to HTTPS.
securityDNSSEC
DNSSEC is not enabled. DNS responses are not cryptographically signed.
securityDomain Age
Domain registered 1.1 years ago (created 2025-08-29).
maturityWHOIS Registration
Domain registered with NAMECHEAP INC.
maturityDNS Configuration
DNS records found. Nameservers: ns64.arzhost.com, ns65.arzhost.com.
transportContent Safety
No harmful content categories detected.
contextSocial Media Presence
No social media links found on the website.
reputationEssential Pages
Found: Contact, About, Privacy Policy, Terms.
contextContent Quality
Website has proper page title and meta description.
contextDomain Authority Rating
Domain Rating of 31/100 based on backlink profile strength.
reputationWhat is cruzdid.com?
Registration & infrastructure
Registration data from WHOIS/RDAP and resolved hosting details.
| Domain | cruzdid.com |
| Created | August 29, 2025 Updated Aug 1, 2026 · Expires Aug 29, 2027 |
| Domain age | 1 year |
| Registrar | NAMECHEAP INC IANA ID: 1068 |
| Abuse contact | [email protected] |
| Domain status | Client Transfer ProhibitedDNSSEC: unsigned |
| Top-level domain | .com Generic TLD |
| SSL certificate | Valid |
| Domain rating | 31/100 |
| Hosting location | 🇨🇦 Canada |
Technology Lookup
Fingerprinted from the site's HTML, response headers and asset URLs.
Discussion