The domain timurwear.mystrikingly.com is registered with an undisclosed registrar. It resolves to IP address 52.84.150.45, hosted by Amazon.com, Inc.. Email delivery is handled by No MX Records Found. No valid SPF record was detected. DMARC protection is missing or unconfigured. Web traffic is secured with an SSL certificate issued by Amazon RSA 2048 M04.
Domain Overview: timurwear.mystrikingly.com
Expires in N/A · DNSSEC: Unsigned
No MX Records Found
Issuer: Amazon RSA 2048 M04 (2 SANs)
Ashburn, Virginia, United States (US)
🌐 Domain & Registration Identity View Full Whois Details →
| Domain | timurwear.mystrikingly.com |
|---|---|
| Website Title | |
| Registered | N/A |
| Expires | N/A |
| Remaining Validity | N/A |
| Domain Age | N/A |
| Registrar | N/A |
| Domain Status | N/A |
| DNSSEC Delegation | Unsigned · Zone not signed with DNSSEC keys |
| Authoritative Nameservers | N/A |
🛡️ Email Security & Deliverability (SPF, DKIM, DMARC) View Complete Email Security Diagnostics →
| Detected Email Provider | 📬 No MX Records Found |
|---|---|
| Primary Mail Server (MX) |
None
|
| SPF Record (Sender Policy) | Missing |
| DKIM Authentication | Not Detected · (No common third-party selector found; custom keys may be configured) |
| DMARC Policy | Missing |
| SMTP Port 25 Status | N/A · Inbound mail server handshake response |
🖥️ Web Server, Hosting & Network View Full Server & Tech Details →
| Web Server Software | CloudFront |
|---|---|
| HTTP Status Code | 403 |
| Server IP (IPv4) | 52.84.150.45 View Geo Details → |
| IPv6 Address (AAAA) | Not Configured |
| Reverse DNS (PTR) |
None Detected (No PTR Record)
|
| Server Location | 📍 Ashburn, Virginia, United States (US) |
| ASN Network & ISP | AS16509 (Amazon.com, Inc.) |
| Hosting Provider | Amazon.com, Inc. |
| Control Panel | Not Detected |
| Technology Stack | No third-party framework or CMS fingerprints detected |
| HTTP Security Headers | None Detected (Missing HSTS / CSP) Audit Details → |
| DNSBL Blacklist Reputation | Clean (0/5 lists) |
🔒 SSL/TLS Certificate Summary View Full SSL Certificate & Chain →
| Primary Hostname (CN) | mystrikingly.com · Multi-Domain SAN (Covers 2 hostnames) |
|---|---|
| SSL Issuer | Amazon RSA 2048 M04 |
| SSL Valid Till | 2027-02-09 |
| Remaining Validity | 137 Days |
| Chain Status | Valid Trusted Chain |
| Signature Algorithm | RSA-SHA256 |
Whois Ownership & Registration for timurwear.mystrikingly.com
📄 View Raw Registry Response ↓OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 0
DNS Records for timurwear.mystrikingly.com
NS Records
No NS records found.
A Records
| Name | Data | Copy |
|---|---|---|
| timurwear.mystrikingly.com. | 52.84.150.45 |
|
| timurwear.mystrikingly.com. | 52.84.150.43 |
|
| timurwear.mystrikingly.com. | 52.84.150.39 |
|
| timurwear.mystrikingly.com. | 52.84.150.63 |
AAAA Records
No AAAA records found.
WWW Records (www.timurwear.mystrikingly.com)
| Type | Host | Value | Copy |
|---|---|---|---|
| A | www.timurwear.mystrikingly.com. | 52.84.150.39 |
|
| A | www.timurwear.mystrikingly.com. | 52.84.150.45 |
|
| A | www.timurwear.mystrikingly.com. | 52.84.150.63 |
|
| A | www.timurwear.mystrikingly.com. | 52.84.150.43 |
MX Records
No MX records found.
TXT Records
No TXT records found.
Email Security (MX, SPF, DKIM, DMARC, SMTP) for timurwear.mystrikingly.com
Mail Exchange (MX) Routing Records
Warning: No MX records were found for timurwear.mystrikingly.com. This domain cannot receive emails.
SPF Record Validation
No SPF record found to validate.
Common DKIM Selectors
No common third-party DKIM selectors found. Custom selectors may be configured.
🔍 Query Custom DKIM Selector
Live DNS Lookup
Using a custom or date-based selector (e.g. crm, newsletter, 2024)? Query its public key live on timurwear.mystrikingly.com:
DMARC Policy Validation
No DMARC record found to validate.
Validation Summary
| DMARC Record Published | Fail No DMARC record was found. |
Optimization Suggestions
A DMARC record is essential for email security. It tells receiving servers what to do with emails that fail SPF and DKIM checks, protecting your domain from spoofing.
Server IP Blacklist Check (52.84.150.45)
SSL/TLS Certificate Details for timurwear.mystrikingly.com
- Issuer: Amazon RSA 2048 M04
- Expires In: 137 Days
- Chain Status: Valid Chain
Main Leaf Certificate
- Common Name:
mystrikingly.com - SANs: DNS:mystrikingly.com, DNS:*.mystrikingly.com
- Organization: N/A
- Validity: Jul 26, 2026 to Feb 09, 2027
- Algorithm: RSA-SHA256
- Common Name: Amazon RSA 2048 M04
- Organization: Amazon
- Valid Till: Aug 24, 2030
- Issuer: Amazon Root CA 1
- Common Name: Amazon Root CA 1
- Organization: Amazon
- Valid Till: Dec 31, 2037
- Issuer: Starfield Services Root Certificate Authority - G2
Website & Server Intelligence for timurwear.mystrikingly.com
Website Identity
| Title | |
|---|---|
| Meta Description | N/A |
Hosting & Server Network
| IP Address | 52.84.150.45 |
|---|---|
| HTTP Status | 403 |
| Hosting Provider | Amazon.com, Inc. |
| Web Server | CloudFront |
| Control Panel | Not Detected |
Technology Profile
No specific third-party frameworks or CMS fingerprints detected.
HTTP Security Headers
| Strict-Transport-Security | Missing |
| Content-Security-Policy | Missing |
| X-Frame-Options | Missing |
| X-Content-Type-Options | Missing |
| Referrer-Policy | Missing |
| Permissions-Policy | Missing |
IP Details & Geolocation
| IP Address | 52.84.150.45 |
|---|---|
| Reverse DNS (PTR) |
None Detected (No PTR Record)
|
| Country | United States (US) |
| Region | Virginia |
| City | Ashburn |
| ZIP Code | N/A |
| ASN | 16509 |
| Organization / ISP | Amazon.com, Inc. |
Understanding Diagnostic Terms for timurwear.mystrikingly.com
Domain Status (EPP)
EPP status codes (e.g., clientTransferProhibited, active) indicating if a domain is locked against unauthorized transfer, pending renewal, or active.
Registrar Information
The authorized or accredited organization managing the domain reservation and authoritative registry delegation.
Nameservers (NS)
Authoritative servers that translate domain names into IP addresses and direct web visitors and mail traffic globally.
A & AAAA Records
Primary address records mapping your domain name directly to standard IPv4 (e.g., 192.0.2.1) and newer IPv6 server network addresses.
MX (Mail Exchange)
Priority-ranked records pointing inbound emails to designated mail server hosts (e.g., Google Workspace, Microsoft 365, Zoho).
SPF & DMARC Security
Email authentication standards that verify authorized sender IPs (SPF) and instruct receiving servers how to enforce security policies (DMARC).
DKIM Signatures
Cryptographic public key in DNS used by receiving mail servers to verify digital signatures on your emails, ensuring messages were not tampered with.
SSL Certificate & Chain
Establishes encrypted HTTPS connections and authenticates domain ownership via an intermediate certificate authority chain.
Hosting Provider & ASN
The physical server infrastructure where website files reside and the autonomous system network (ASN) routing global traffic.
Reverse DNS (PTR)
Pointer (PTR) records that map a server's IP address back to its canonical hostname, verifying server identity and preventing email spam rejection.
HTTP Security Headers
Directives like HSTS, CSP, and X-Frame-Options instructed by the server to protect browser visitors against XSS, clickjacking, and packet sniffing.
⚠️ Report Limitations & Data Sources
- Data Currency: This report uses cached registry and DNS data (freshened within 4 hours) for high-speed resolution. Click "🔄 Refresh Live" to query directly against authoritative registries.
- DNS Resolution & Propagation: Records are queried via Google Public DNS-over-HTTPS. Global DNS propagation may take up to 24–48 hours across different regional ISP resolvers during recent DNS record changes.
- Completeness & Scope: This diagnostic tool analyzes standard authoritative records (A, AAAA, MX, NS, TXT, CNAME, SOA). It does not perform invasive brute-force subdomain scans or unauthenticated DNS zone transfers.
- Email Deliverability & Reputation: The security analysis (SPF, DKIM, DMARC, and Port 25 SMTP handshake) reflects public DNS policies and inbound connection states. Recipient spam filters evaluate internal headers that cannot be checked from outside.
- Reverse Proxies & CDNs: If a website is behind Cloudflare, Fastly, or another CDN/reverse proxy, the detected IP, web server software, and SSL edge certificate reflect the proxy tier.