myipayrollcard.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 57 days left11 years old
75
myipayrollcard.com was registered on 21 Nov 2014 via Tucows Domains Inc. and the registry expiry is 21 Nov 2026. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/myipayrollcard.com.
myipayrollcard.com publishes 2 nameservers. DNSSEC is signed.
myipayrollcard.com has 2 IPv4 addresses (188.114.96.4, 188.114.97.4) and 2 IPv6 addresses (2a06:98c1:3120::4, 2a06:98c1:3121::4). The geolocation database places 188.114.96.4 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 57 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, Cloudflare Bot Management, Google Analytics and HSTS. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for myipayrollcard.com in the checks that ran.
Domain · RDAP/WHOIS
myipayrollcard.com was registered on 21 Nov 2014 via Tucows Domains Inc.. The registry returned 2 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/myipayrollcard.com.
| Registered | since 21 Nov 2014 |
|---|---|
| Created | 21 November 2014 |
| Updated | 20 November 2025 |
| Expires | 21 November 2026 |
| Registrar | Tucows Domains Inc. |
| Status | client transfer prohibited, client update prohibited |
| Nameservers | tony.ns.cloudflare.com, tori.ns.cloudflare.com |
| DNSSEC | yes |
| Source | https://rdap.verisign.com/com/v1/domain/myipayrollcard.com |
myipayrollcard.com 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.
myipayrollcard.com 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.
Nameserver tony.ns.cloudflare.com is published for myipayrollcard.com in the registration record from https://rdap.verisign.com/com/v1/domain/myipayrollcard.com.
Nameserver tori.ns.cloudflare.com is published for myipayrollcard.com in the registration record from https://rdap.verisign.com/com/v1/domain/myipayrollcard.com.
DNS
myipayrollcard.com has 4 address records, 5 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 188.114.96.4, 188.114.97.4 |
|---|---|
| AAAA | 2a06:98c1:3120::4, 2a06:98c1:3121::4 |
| NS | tony.ns.cloudflare.com, tori.ns.cloudflare.com |
| MX | aspmx.l.google.com (1) Google, alt1.aspmx.l.google.com (5) Google, alt2.aspmx.l.google.com (5) Google, aspmx2.googlemail.com (10) Google, aspmx3.googlemail.com (10) Google |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 188.114.96.4 answers for myipayrollcard.com at resolver 1.1.1.1:53.
IPv4 address 188.114.97.4 answers for myipayrollcard.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::4 answers for myipayrollcard.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::4 answers for myipayrollcard.com 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 aspmx2.googlemail.com has preference 10. The host is recognised as Google.
Mail exchanger aspmx3.googlemail.com has preference 10. The host is recognised as Google.
Hosting and geo
myipayrollcard.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 188.114.96.4 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for myipayrollcard.com is valid, with 57 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | myipayrollcard.com |
| Valid from | 28 September 2026 |
| Valid until | 27 December 2026 |
| Days left | 57 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.myipayrollcard.com, myipayrollcard.com.
Tech stack
Tech detection checked the fetched homepage and named 4 products. Source: wappalyzergo.
- Cloudflare · CDN
- Cloudflare Bot Management · Security
- Google Analytics · Analytics
- HSTS · Security
Cloudflare is filed under CDN.
Cloudflare Bot Management is filed under Security.
Google Analytics is filed under Analytics.
HSTS is filed under Security.
On-page checks
The homepage returned HTTP 200 in 26 ms. The target title is 16 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 26 ms |
| Title length | 16 yes |
| Quoted title | "iPay Banking App" |
| Meta description | "Welcome to a better payday. The iPay Prepaid Mastercard® provides you a safe, convenient way to receive your pay, make purchases, pay bills, get cash––and easily manage your balance, track your spending, and get instant notifications with the iPay Mobile App." yes |
| H1 count | 0 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | noindex |
| Canonical | — |
| Language | en |
| Links | 41 |
| Images | 182 |
| 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 myipayrollcard.com 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 | no |
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 5 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 5 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
First checked on 30 October 2026; changes will appear here.
Questions
Is myipayrollcard.com 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 myipayrollcard.com?
myipayrollcard.com is placed in Toronto, Canada.
When does myipayrollcard.com expire?
myipayrollcard.com expires on 21 November 2026 according to https://rdap.verisign.com/com/v1/domain/myipayrollcard.com.
Who owns myipayrollcard.com?
The registry did not return a person or a company for myipayrollcard.com. RDAP often redacts the registrant. The registrar on file is Tucows Domains Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/myipayrollcard.com at 2026-10-30T14:05:36Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:05:36Z
- TLS source tls:443 at 2026-10-30T14:05:36Z
- HTTP source https://myipayrollcard.com/ at 2026-10-30T14:05:36Z
- Tech source wappalyzergo at 2026-10-30T14:05:36Z
- Geo source db-ip at 2026-10-30T14:05:36Z
- Safety source family DNS and local lists at 2026-10-30T14:05:36Z
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.