crackingpatching.com

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

Online · 200Family DNS blockedSSL: 30 days left11 years oldTranco #740527

One re-check per domain each UTC day.

50

crackingpatching.com was registered on 15 Feb 2015 via GoDaddy.com, LLC and the registry expiry is 15 Feb 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/crackingpatching.com.

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

crackingpatching.com has 2 IPv4 addresses (188.114.96.4, 188.114.97.4) and 2 IPv6 addresses (2a06:98c1:3120::3, 2a06:98c1:3121::3). The geolocation database places 188.114.96.4 in Toronto, Canada.

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

Tech detection named Cloudflare, Google AdSense, HTTP/3, MySQL, PHP, Twitter, WordPress, WordPress Super Cache, Yoast SEO, jQuery and jQuery Migrate. The fingerprints ran on the homepage that was already downloaded.

Domain · RDAP/WHOIS

crackingpatching.com was registered on 15 Feb 2015 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.verisign.com/com/v1/domain/crackingpatching.com.

Registeredsince 15 Feb 2015
Created15 February 2015
Updated16 February 2025
Expires15 February 2027
RegistrarGoDaddy.com, LLC
Statusclient delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
Nameserversalan.ns.cloudflare.com, joan.ns.cloudflare.com
DNSSECno
Sourcehttps://rdap.verisign.com/com/v1/domain/crackingpatching.com

crackingpatching.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.

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

crackingpatching.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.

crackingpatching.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 alan.ns.cloudflare.com is published for crackingpatching.com in the registration record from https://rdap.verisign.com/com/v1/domain/crackingpatching.com.

Nameserver joan.ns.cloudflare.com is published for crackingpatching.com in the registration record from https://rdap.verisign.com/com/v1/domain/crackingpatching.com.

DNS

crackingpatching.com has 4 address records, 2 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A188.114.96.4, 188.114.97.4
AAAA2a06:98c1:3120::3, 2a06:98c1:3121::3
NSalan.ns.cloudflare.com, joan.ns.cloudflare.com
MXsmtp.secureserver.net (0) GoDaddy, mailstore1.secureserver.net (10) GoDaddy
SPFabsent
DMARCabsent
CAA—
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 188.114.96.4 answers for crackingpatching.com at resolver 1.1.1.1:53.

IPv4 address 188.114.97.4 answers for crackingpatching.com at resolver 1.1.1.1:53.

IPv6 address 2a06:98c1:3120::3 answers for crackingpatching.com at resolver 1.1.1.1:53.

IPv6 address 2a06:98c1:3121::3 answers for crackingpatching.com at resolver 1.1.1.1:53.

Mail exchanger smtp.secureserver.net has preference 0. The host is recognised as GoDaddy.

Mail exchanger mailstore1.secureserver.net has preference 10. The host is recognised as GoDaddy.

Hosting and geo

crackingpatching.com is placed in Toronto, Canada by the local geolocation database (db-ip).

Address188.114.96.4
CountryCanada
CityToronto
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

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

IssuerWE1
Subjectcrackingpatching.com
Valid from2 September 2026
Valid until1 December 2026
Days left30
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: *.crackingpatching.com, crackingpatching.com.

Tech stack

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

  • Cloudflare · CDN
  • Google AdSense · Advertising
  • HTTP/3 · Miscellaneous
  • MySQL · Databases
  • PHP · Programming languages
  • Twitter · Widgets
  • WordPress · CMS, Blogs
  • WordPress Super Cache · Caching, WordPress plugins
  • Yoast SEO · SEO, WordPress plugins
  • jQuery · JavaScript libraries
  • jQuery Migrate · JavaScript libraries

Cloudflare is filed under CDN.

Google AdSense is filed under Advertising.

HTTP/3 is filed under Miscellaneous.

MySQL is filed under Databases.

PHP is filed under Programming languages.

Twitter is filed under Widgets.

WordPress is filed under CMS, Blogs.

WordPress Super Cache is filed under Caching, WordPress plugins.

Yoast SEO is filed under SEO, WordPress plugins.

jQuery is filed under JavaScript libraries.

jQuery Migrate is filed under JavaScript libraries.

On-page checks

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

Status200
TTFB90 ms
Title length43 yes
Quoted title"CrackingPatching - Believe us we can do it!"
Meta description"Believe us we can do it!" yes
H1 count0
HSTSno no
CSPno
X-Frame-Options—
Robots metaindex, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
Canonicalhttps://crackingpatching.com/
Languageen-US
Links155
Images32
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 crackingpatching.com is blocked, and URLhaus is clear. Source: family DNS and local lists.

Family DNSblocked
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSno
CSPno

Cloudflare family DNS returned a block for crackingpatching.com. That resolver covers adult and malware names.

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 0 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: dns a changed from 188.114.96.3,188.114.97.3 to 188.114.96.4,188.114.97.4.
  • October 2026: dns aaaa changed from 2a06:98c1:3120::4,2a06:98c1:3121::4 to 2a06:98c1:3120::3,2a06:98c1:3121::3.

Questions

Is crackingpatching.com safe?

Cloudflare family DNS returned a block for crackingpatching.com. That resolver covers adult and malware names.

Who hosts crackingpatching.com?

crackingpatching.com is placed in Toronto, Canada.

When does crackingpatching.com expire?

crackingpatching.com expires on 15 February 2027 according to https://rdap.verisign.com/com/v1/domain/crackingpatching.com.

Who owns crackingpatching.com?

The registry did not return a person or a company for crackingpatching.com. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.

Sources

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

Methodology

Related reports

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

.com GoDaddy.com, LLC

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.