string.design was registered with whois.nic.design on 18 Dec 2014 and is hosted on AS202675 Keliweb S.R.L in Italy. Its SSL certificate from Let's Encrypt expired on 21 Dec 2023, and the site does not support HTTP/3.
What security vendors and the WOT community say about this domain.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
Is string.design’s name taken on other extensions?
2 technologies detected across 2 categories.
Detected from headers, page source and DNS · Automatic and may be incomplete · Suggest a correction
Every IP address string.design resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| string.design | 185.221.175.3 | 14400 |
| Host | Mail server | TTL |
|---|---|---|
| string.design | 0 string.design | 14400 |
| Host | Name server | TTL |
|---|---|---|
| string.design | dns.keliweb.com | 21600 |
| string.design | dns.keliweb.eu | 21600 |
| string.design | dns.keliweb.net | 21600 |
| string.design | dns.keliweb.org | 21600 |
| Host | Text | TTL |
|---|---|---|
| string.design | "google-site-verification=0IBThHWrCiA1S-yHY_cFKsQNSr4E7m0FCjudIln0R3Y" | 14400 |
| string.design | "v=spf1 +a +mx +ip4:185.221.175.3 ~all" | 14400 |
| Host | Start of authority | TTL |
|---|---|---|
| string.design | dns.keliweb.com server.keliweb.com 2023092301 3600 1800 1209600 86400 | 21600 |
Other domains served from 185.221.175.3. Normal for shared hosting and CDNs.
No reviews yet. Used string.design? Be the first to say how it went.
Reviews are from CubDomain users and are separate from the security verdicts above.
Common questions, answered from this report's data.
string.design has no community safety rating yet. Its SSL certificate expired on 21 Dec 2023. See Security →
string.design is registered through whois.nic.design. See WHOIS →
string.design was registered on 18 Dec 2014, making it 11 years old. See Overview →
string.design is served from 1 IP address, mainly on AS202675 Keliweb S.R.L in Italy. See Hosting →
We detected 2 technologies, including WordPress and jQuery. See Built with →
Raw registry data for string.design. May be redacted by privacy services.
% IANA WHOIS server % for more information on IANA, visit http://www.iana.org % This query returned 1 object domain: DESIGN organisation: Registry Services, LLC address: 2155 E. GoDaddy Way address: Tempe AZ 85284 address: United States of America (the) contact: administrative name: IANA Contact organisation: GoDaddy Registry address: 2155 E. GoDaddy Way address: Tempe AZ 85284 address: United States of America (the) phone: +1 480-505-8800 fax-no: +1 480-624-2546 e-mail: [email protected] contact: technical name: IANA Contact organisation: GoDaddy Registry address: 2155 E. GoDaddy Way address: Tempe AZ 85284 address: United States of America (the) phone: +1 480-505-8800 fax-no: +1 480-624-2546 e-mail: [email protected] nserver: A.NIC.DESIGN 2001:dcd:1:0:0:0:0:10 37.209.192.10 nserver: B.NIC.DESIGN 2001:dcd:2:0:0:0:0:10 37.209.194.10 nserver: C.NIC.DESIGN 2001:dcd:3:0:0:0:0:10 37.209.196.10 nserver: X.NIC.DESIGN 156.154.172.82 2610:a1:1074:0:0:0:1:82 nserver: Y.NIC.DESIGN 156.154.173.82 2610:a1:1075:0:0:0:1:82 nserver: Z.NIC.DESIGN 156.154.174.82 2610:a1:1076:0:0:0:1:82 ds-rdata: 50422 8 2 400c06349da05ff7c9b9d8c11857e8e9c3ce947ea05cc4c7c6de878bf2a496ee ds-rdata: 27199 8 2 eaec6e1b661b0264846ff8f70858cc63711f0627781386b9024360656679ecf5 whois: whois.nic.design status: ACTIVE remarks: Registration information: http://nic.design/ created: 2014-12-18 changed: 2023-08-15 source: IANA
The first response from http://www.string.design, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with string.design. Data is collected independently from public sources and some figures are estimates, provided for information only.
Spam and malware blocklists for the site's IP and mail servers.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.