Registered 11 years ago, on no blocklists we checked, valid HTTPS, the site answered 200 in 792 ms.
Rule-based: domain age, blocklists, TLS. A heuristic, not a guarantee.

| A | 52.74.197.173 52.74.164.250 18.139.21.177 |
|---|---|
| NS | ns-405.awsdns-50.com ns-1097.awsdns-09.org ns-931.awsdns-52.net ns-1880.awsdns-43.co.uk |
| registrar | GoDaddy.com, LLC |
|---|---|
| registered | 2016-04-20 |
| expires | 2027-04-20 |
| last changed | 2025-03-19 |
| nameservers | ns-1097.awsdns-09.org ns-1880.awsdns-43.co.uk ns-405.awsdns-50.com ns-931.awsdns-52.net |
| status | client delete prohibited client renew prohibited client transfer prohibited client update prohibited |
| valid | yes |
|---|---|
| issuer | Amazon |
| covers | packzy.com, userapp.packzy.com, merchant.packzy.com, rider.packzy.com, www.packzy.com, admin.packzy.com, portal.packzy.com |
| protocol | TLSv1.3 |
Domain is not signed with DNSSEC
| SPF | none |
|---|---|
| DMARC | warning policy none |
| DKIM | none of 1 common selectors |
Whether mail claiming to be from this domain can be checked as genuine.
Green: clean. Red: listed. Grey: the list did not answer.
Agents get this as data. Bought through the API, the checks behind this page cost $0.070: profile $0.025 + trust $0.020 + screenshot $0.020 + site status $0.005.
MCP: add https://how.is/mcp to Claude, Codex or Cursor
(one-line install) and ask for domain_trust on packzy.com.
Reference: /llms.txt.
IPv6. Does packzy.com work over IPv6? See the live check on aaaa.bot — website, mail and nameservers, graded A–F.
Watch packzy.com. DNS read at the source every 5 minutes; certificate, blocklists and expiry every 6 hours. You get an email only when something changes.
Watch — $1 / 30 days