trackmyshipment.co
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 87 days left9 years oldTranco #933436
100
trackmyshipment.co was registered on 18 Sep 2017 via GoDaddy.com, LLC and the registry expiry is 17 Sep 2027. WHOIS data came from RDAP at https://rdap.registry.co/co/domain/trackmyshipment.co.
trackmyshipment.co publishes 2 nameservers. DNSSEC is signed.
trackmyshipment.co has 3 IPv4 addresses (104.26.4.229, 104.26.5.229, 172.67.68.72) and 3 IPv6 addresses (2606:4700:20::681a:4e5, 2606:4700:20::681a:5e5, 2606:4700:20::ac43:4448). The geolocation database places 104.26.4.229 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 87 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Amazon S3, Amazon Web Services, Cloudflare, Google Cloud, Google Cloud CDN and HSTS. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for trackmyshipment.co in the checks that ran.
Domain · RDAP/WHOIS
trackmyshipment.co was registered on 18 Sep 2017 via GoDaddy.com, LLC. The registry returned 5 status values and 2 nameservers from https://rdap.registry.co/co/domain/trackmyshipment.co.
| Registered | since 18 Sep 2017 |
|---|---|
| Created | 18 September 2017 |
| Updated | 18 September 2026 |
| Expires | 17 September 2027 |
| Registrar | GoDaddy.com, LLC |
| Status | client renew prohibited, client transfer prohibited, client update prohibited, client delete prohibited, auto renew period |
| Nameservers | lou.ns.cloudflare.com, sue.ns.cloudflare.com |
| DNSSEC | yes |
| Source | https://rdap.registry.co/co/domain/trackmyshipment.co |
trackmyshipment.co carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.
trackmyshipment.co carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.
trackmyshipment.co carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
trackmyshipment.co carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.
Nameserver lou.ns.cloudflare.com is published for trackmyshipment.co in the registration record from https://rdap.registry.co/co/domain/trackmyshipment.co.
Nameserver sue.ns.cloudflare.com is published for trackmyshipment.co in the registration record from https://rdap.registry.co/co/domain/trackmyshipment.co.
DNS
trackmyshipment.co has 6 address records, 5 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.26.4.229, 104.26.5.229, 172.67.68.72 |
|---|---|
| AAAA | 2606:4700:20::681a:4e5, 2606:4700:20::681a:5e5, 2606:4700:20::ac43:4448 |
| NS | lou.ns.cloudflare.com, sue.ns.cloudflare.com |
| MX | aspmx.l.google.com (1) Google, alt1.aspmx.l.google.com (5) Google, alt2.aspmx.l.google.com (5) Google, alt3.aspmx.l.google.com (10) Google, alt4.aspmx.l.google.com (10) Google |
| SPF | present |
| DMARC | present |
| CAA | issue comodoca.com, issue digicert.com; cansignhttpexchanges=yes, issue letsencrypt.org, issue pki.goog; cansignhttpexchanges=yes, issue ssl.com, issuewild comodoca.com, issuewild digicert.com; cansignhttpexchanges=yes, issuewild letsencrypt.org, issuewild pki.goog; cansignhttpexchanges=yes, issuewild ssl.com |
| Wildcard | off |
| DNSSEC | signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at trackmyshipment.co is "v=spf1 include:spf.mandrillapp.com include:_spf.google.com -all".
The DMARC text record at _dmarc.trackmyshipment.co is "v=DMARC1; p=quarantine; rua=mailto:[email protected]; pct=100;".
IPv4 address 104.26.4.229 answers for trackmyshipment.co at resolver 1.1.1.1:53.
IPv4 address 104.26.5.229 answers for trackmyshipment.co at resolver 1.1.1.1:53.
IPv4 address 172.67.68.72 answers for trackmyshipment.co at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:4e5 answers for trackmyshipment.co at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::681a:5e5 answers for trackmyshipment.co at resolver 1.1.1.1:53.
IPv6 address 2606:4700:20::ac43:4448 answers for trackmyshipment.co at resolver 1.1.1.1:53.
Mail exchanger aspmx.l.google.com has preference 1. The host is recognised as Google.
Mail exchanger alt1.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt2.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt3.aspmx.l.google.com has preference 10. The host is recognised as Google.
Mail exchanger alt4.aspmx.l.google.com has preference 10. The host is recognised as Google.
Hosting and geo
trackmyshipment.co is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.26.4.229 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for trackmyshipment.co is valid, with 87 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | trackmyshipment.co |
| Valid from | 28 October 2026 |
| Valid until | 26 January 2027 |
| Days left | 87 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.trackmyshipment.co, trackmyshipment.co.
Tech stack
Tech detection checked the fetched homepage and named 6 products. Source: wappalyzergo.
- Amazon S3 · CDN
- Amazon Web Services · PaaS
- Cloudflare · CDN
- Google Cloud · IaaS
- Google Cloud CDN · CDN
- HSTS · Security
Amazon S3 is filed under CDN.
Amazon Web Services is filed under PaaS.
Cloudflare is filed under CDN.
Google Cloud is filed under IaaS.
Google Cloud CDN is filed under CDN.
HSTS is filed under Security.
On-page checks
The homepage returned HTTP 200 in 30 ms. The target title is 19 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 30 ms |
| Title length | 19 yes |
| Quoted title | "Track Your Shipment" |
| Meta description | none no |
| H1 count | 0 |
| HSTS | yes yes |
| CSP | yes |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | noindex |
| Canonical | — |
| Language | en |
| Links | 0 |
| Images | 0 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Security
Family DNS for trackmyshipment.co is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | yes |
| CSP | yes |
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
Score breakdown
Availability 25 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 20 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 15 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 15 of 15. Points only when the checks ran and came back clean. Unknown is not clean.
Domain age 5 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: rdap created changed from empty to 2017-09-18T01:44:39.0Z.
- October 2026: rdap dnssec changed from unknown to yes.
- October 2026: rdap expires changed from empty to 2027-09-17T23:59:59.0Z.
- October 2026: rdap nameservers changed from empty to lou.ns.cloudflare.com,sue.ns.cloudflare.com.
- October 2026: rdap registered changed from unknown to yes.
- October 2026: rdap registrar changed from empty to GoDaddy.com, LLC.
- October 2026: rdap statuses changed from empty to auto renew period,client delete prohibited,client renew prohibited,client transfer prohibited,client update prohibited.
- October 2026: rdap updated changed from empty to 2026-09-18T10:23:57.0Z.
Questions
Is trackmyshipment.co safe?
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
Who hosts trackmyshipment.co?
trackmyshipment.co is placed in Toronto, Canada.
When does trackmyshipment.co expire?
trackmyshipment.co expires on 17 September 2027 according to https://rdap.registry.co/co/domain/trackmyshipment.co.
Who owns trackmyshipment.co?
The registry did not return a person or a company for trackmyshipment.co. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.registry.co/co/domain/trackmyshipment.co at 2026-10-30T13:39:37Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:39:37Z
- TLS source tls:443 at 2026-10-30T13:39:37Z
- HTTP source https://trackmyshipment.co/ at 2026-10-30T13:39:37Z
- Tech source wappalyzergo at 2026-10-30T13:39:37Z
- Geo source db-ip at 2026-10-30T13:39:37Z
- Safety source family DNS and local lists at 2026-10-30T13:39:37Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
Owner of this site?
Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.
How to read this report
The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.