vsimcard.com

Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .

Online · 200SafeSSL: 64 days left14 years old

One re-check per domain each UTC day.

80

vsimcard.com was registered on 1 Dec 2011 via OVH sas and the registry expiry is 1 Dec 2026. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/vsimcard.com.

vsimcard.com publishes 2 nameservers. DNSSEC is not signed.

vsimcard.com has 1 IPv4 address (49.13.21.171). The geolocation database places 49.13.21.171 in Falkenstein, Germany.

The TLS certificate from YE1 is valid and has 64 days left (TLS 1.3). The homepage answered HTTP 200.

Tech detection named HSTS, Nginx and Ubuntu. The fingerprints ran on the homepage that was already downloaded.

No safety warning was recorded for vsimcard.com in the checks that ran.

Domain · RDAP/WHOIS

vsimcard.com was registered on 1 Dec 2011 via OVH sas. The registry returned 2 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/vsimcard.com.

Registeredsince 1 Dec 2011
Created1 December 2011
Updated2 December 2025
Expires1 December 2026
RegistrarOVH sas
Statusclient delete prohibited, client transfer prohibited
Nameserversdns16.ovh.net, ns16.ovh.net
DNSSECno
Sourcehttps://rdap.verisign.com/com/v1/domain/vsimcard.com

vsimcard.com 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.

vsimcard.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 dns16.ovh.net is published for vsimcard.com in the registration record from https://rdap.verisign.com/com/v1/domain/vsimcard.com.

Nameserver ns16.ovh.net is published for vsimcard.com in the registration record from https://rdap.verisign.com/com/v1/domain/vsimcard.com.

DNS

vsimcard.com has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.

A49.13.21.171
AAAA—
NSdns16.ovh.net, ns16.ovh.net
MXmail.vsimcard.com (0)
SPFpresent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

The SPF text record at vsimcard.com is "v=spf1 a mx -all".

IPv4 address 49.13.21.171 answers for vsimcard.com at resolver 1.1.1.1:53.

Mail exchanger mail.vsimcard.com has preference 0.

Hosting and geo

vsimcard.com is placed in Falkenstein, Germany by the local geolocation database (db-ip).

Address49.13.21.171
CountryGermany
CityFalkenstein
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for vsimcard.com is valid, with 64 days left and 2 subject alternative names. Source: tls:443.

IssuerYE1
Subjectvsimcard.com
Valid from6 October 2026
Valid until4 January 2027
Days left64
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: imap.vsimcard.com, vsimcard.com.

Tech stack

Tech detection checked the fetched homepage and named 3 products. Source: wappalyzergo.

  • HSTS · Security
  • Nginx · Web servers, Reverse proxies
  • Ubuntu · Operating systems

HSTS is filed under Security.

Nginx is filed under Web servers, Reverse proxies.

Ubuntu is filed under Operating systems.

On-page checks

The homepage returned HTTP 200 in 27 ms. The target title is 8 characters and the page has 0 H1 headings.

Status200
TTFB27 ms
Title length8 yes
Quoted title"Vsimcard"
Meta descriptionnone no
H1 count0
HSTSyes yes
CSPno
X-Frame-OptionsSAMEORIGIN
Robots meta—
Canonical—
Languageen
Links0
Images0
Faviconyes

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 vsimcard.com is clear, and URLhaus is clear. Source: family DNS and local lists.

Family DNSclear
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSyes
CSPno

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 10 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 Falkenstein.
  • October 2026: geo country changed from empty to Germany.

Questions

Is vsimcard.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 vsimcard.com?

vsimcard.com is placed in Falkenstein, Germany.

When does vsimcard.com expire?

vsimcard.com expires on 1 December 2026 according to https://rdap.verisign.com/com/v1/domain/vsimcard.com.

Who owns vsimcard.com?

The registry did not return a person or a company for vsimcard.com. RDAP often redacts the registrant. The registrar on file is OVH sas.

Sources

  • RDAP source https://rdap.verisign.com/com/v1/domain/vsimcard.com at 2026-10-30T14:19:27Z
  • DNS source 1.1.1.1:53 at 2026-10-30T14:19:27Z
  • TLS source tls:443 at 2026-10-30T14:19:27Z
  • HTTP source https://vsimcard.com/ at 2026-10-30T14:19:27Z
  • Tech source wappalyzergo at 2026-10-30T14:19:27Z
  • Geo source db-ip at 2026-10-30T14:19:27Z
  • Safety source family DNS and local lists at 2026-10-30T14:19:27Z

Methodology

Related reports

No other indexable reports share this TLD, host, or registrar yet.

.com OVH sas

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.

Removal policy

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.