domain/daharlogistics.com
- Registration data
RDAP - DNS records
A, AAAA, MX, NS, TXT, CAA, SOA - Email policy
_dmarc - TLS certificate
port 443 - Website snapshot
HTTP - Comparing with history
whois.is archive
RDAPA, AAAA, MX, NS, TXT, CAA, SOA_dmarcport 443HTTPwhois.is archivedaharlogistics.com was registered in November 2025 with DropCatch.com 378, and is due to expire in November 2026. Its website was online at the last check, served from Amazon.com's network. daharlogistics.com doesn't receive email: it publishes no mail servers.
Based on what we observed, its registration expires in 5 days.
| Type | Value |
|---|---|
| A | 13.223.25.84 AS14618 · Amazon.com, Inc. · US |
| A | 54.243.117.197 AS14618 · Amazon.com, Inc. · US |
| AAAA | 2600:1f18:4ae:c605:dd5d:b838:5816:d7fb AS14618 · Amazon.com, Inc. · US |
| AAAA | 2600:1f18:4ae:c606:78d4:4260:db4e:aeee AS14618 · Amazon.com, Inc. · US |
| NS | nsg1.namebrightdns.com |
| NS | nsg2.namebrightdns.com |
| TXT | afternic-verification-G9G3tM8T8EwEizzPzjGJWF |
| TXT | v=spf1 -all |
| SOA | ns1.namebrightdns.com dns.namebright.com 2026112101 |
A network is whoever runs the servers behind the address. With a CDN such as Cloudflare in front, that is the CDN, not the company hosting the site behind it.
We didn't recognise any technology on the homepage.
The site blocks automated reading (HTTP 403, Cloudflare challenge), so we can't read its business details.
First observation recorded. Every change from here on is preserved and shown here.
Most registries now keep the registrant's details private, and whois.is doesn't show them. daharlogistics.com is registered through DropCatch.com 378.
daharlogistics.com was registered on 26 Nov 2025, making it 11 months old.
The registry lists 26 Nov 2026 as the expiry date, 5 days from now. Most domains renew automatically before then.
daharlogistics.com's website is served from Amazon.com's network.
No one: daharlogistics.com publishes no MX records, so it can't receive email.
It was up when we last checked, 4 hours ago (21 Nov 2026), answering with HTTP 403. That shows how it was then, not a guarantee of right now.