visacardchecker.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 41 days left8 years old
65
visacardchecker.com was registered on 30 Apr 2018 via Name.com, Inc. and the registry expiry is 30 Apr 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/visacardchecker.com.
visacardchecker.com publishes 4 nameservers. DNSSEC is not signed.
visacardchecker.com has 4 IPv4 addresses (216.239.32.21, 216.239.34.21, 216.239.36.21, 216.239.38.21). The geolocation database places 216.239.32.21 in Mountain View, United States.
The TLS certificate from WR3 is valid and has 41 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Blogger, Cloudflare, Google AdSense, Google Analytics, Google Hosted Libraries, Google Tag Manager, Java, OpenGSE, Python, YouTube, cdnjs and jQuery. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for visacardchecker.com in the checks that ran.
Domain · RDAP/WHOIS
visacardchecker.com was registered on 30 Apr 2018 via Name.com, Inc.. The registry returned 1 status value and 4 nameservers from https://rdap.verisign.com/com/v1/domain/visacardchecker.com.
| Registered | since 30 Apr 2018 |
|---|---|
| Created | 30 April 2018 |
| Updated | 18 April 2026 |
| Expires | 30 April 2027 |
| Registrar | Name.com, Inc. |
| Status | client transfer prohibited |
| Nameservers | ns1hwy.name.com, ns2nsw.name.com, ns3dgr.name.com, ns4fmx.name.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/visacardchecker.com |
visacardchecker.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.
Nameserver ns1hwy.name.com is published for visacardchecker.com in the registration record from https://rdap.verisign.com/com/v1/domain/visacardchecker.com.
Nameserver ns2nsw.name.com is published for visacardchecker.com in the registration record from https://rdap.verisign.com/com/v1/domain/visacardchecker.com.
Nameserver ns3dgr.name.com is published for visacardchecker.com in the registration record from https://rdap.verisign.com/com/v1/domain/visacardchecker.com.
Nameserver ns4fmx.name.com is published for visacardchecker.com in the registration record from https://rdap.verisign.com/com/v1/domain/visacardchecker.com.
DNS
visacardchecker.com has 4 address records, 0 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 216.239.32.21, 216.239.34.21, 216.239.36.21, 216.239.38.21 |
|---|---|
| AAAA | — |
| NS | ns1hwy.name.com, ns2nsw.name.com, ns3dgr.name.com, ns4fmx.name.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 216.239.32.21 answers for visacardchecker.com at resolver 1.1.1.1:53.
IPv4 address 216.239.34.21 answers for visacardchecker.com at resolver 1.1.1.1:53.
IPv4 address 216.239.36.21 answers for visacardchecker.com at resolver 1.1.1.1:53.
IPv4 address 216.239.38.21 answers for visacardchecker.com at resolver 1.1.1.1:53.
Hosting and geo
visacardchecker.com is placed in Mountain View, United States by the local geolocation database (db-ip).
| Address | 216.239.32.21 |
|---|---|
| Country | United States |
| City | Mountain View |
| Source | db-ip |
SSL/TLS
The certificate for visacardchecker.com is valid, with 41 days left and 1 subject alternative name. Source: tls:443.
| Issuer | WR3 |
|---|---|
| Subject | visacardchecker.com |
| Valid from | 12 September 2026 |
| Valid until | 11 December 2026 |
| Days left | 41 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: visacardchecker.com.
Tech stack
Tech detection checked the fetched homepage and named 12 products. Source: wappalyzergo.
- Blogger · Blogs
- Cloudflare · CDN
- Google AdSense · Advertising
- Google Analytics · Analytics
- Google Hosted Libraries · CDN
- Google Tag Manager · Tag managers
- Java · Programming languages
- OpenGSE · Web servers
- Python · Programming languages
- YouTube · Video players
- cdnjs · CDN
- jQuery · JavaScript libraries
Blogger is filed under Blogs.
Cloudflare is filed under CDN.
Google AdSense is filed under Advertising.
Google Analytics is filed under Analytics.
Google Hosted Libraries is filed under CDN.
Google Tag Manager is filed under Tag managers.
Java is filed under Programming languages.
OpenGSE is filed under Web servers.
Python is filed under Programming languages.
YouTube is filed under Video players.
cdnjs is filed under CDN.
jQuery is filed under JavaScript libraries.
On-page checks
The homepage returned HTTP 200 in 20 ms. The target title is 21 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 20 ms |
| Title length | 21 yes |
| Quoted title | "bin visa card checker" |
| Meta description | "✅ How to get a free credit card || The golden website to generate and test electronic payment card || visacardchecker.com" yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | index, follow |
| Canonical | https://www.visacardchecker.com/ |
| Language | — |
| Links | 296 |
| Images | 3 |
| 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 visacardchecker.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 | no |
| 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 0 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 0 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: geo city changed from empty to Mountain View.
- October 2026: geo country changed from empty to United States.
Questions
Is visacardchecker.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 visacardchecker.com?
visacardchecker.com is placed in Mountain View, United States.
When does visacardchecker.com expire?
visacardchecker.com expires on 30 April 2027 according to https://rdap.verisign.com/com/v1/domain/visacardchecker.com.
Who owns visacardchecker.com?
The registry did not return a person or a company for visacardchecker.com. RDAP often redacts the registrant. The registrar on file is Name.com, Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/visacardchecker.com at 2026-10-30T14:19:10Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:19:10Z
- TLS source tls:443 at 2026-10-30T14:19:10Z
- HTTP source https://visacardchecker.com/ at 2026-10-30T14:19:10Z
- Tech source wappalyzergo at 2026-10-30T14:19:10Z
- Geo source db-ip at 2026-10-30T14:19:10Z
- Safety source family DNS and local lists at 2026-10-30T14:19:10Z
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.