retty.me was registered with GMO INTERNET, INC. on 15 Apr 2011 and is hosted on AS54113 Fastly Inc. in United States of America. Its SSL certificate from DigiCert Inc expired on 21 May 2024, and the site does not support HTTP/3. WOT's community rates its safety excellent (82/100).
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 retty.me’s name taken on other extensions?
Estimated visitors and engagement.
| Top countries | Share | Visits | Desktop | Mobile |
|---|---|---|---|---|
| Japan | 98.8% | 13,599,705 | 12.4% | 87.6% |
| Taiwan | 0.3% | 44,397 | 21.7% | 78.3% |
| South Korea | 0.3% | 38,972 | 11.6% | 88.4% |
| United States | 0.3% | 37,112 | 64.9% | 35.1% |
| Indonesia | 0.1% | 13,677 | 0.4% | 99.6% |
2 technologies detected across 2 categories.
Detected from headers, page source and DNS · Automatic and may be incomplete · Suggest a correction
Every IP address retty.me resolves to, and where it's hosted.
| Host | IPv4 address | TTL |
|---|---|---|
| retty.me | 151.101.130.133 | 60 |
| retty.me | 151.101.194.133 | 60 |
| retty.me | 151.101.2.133 | 60 |
| retty.me | 151.101.66.133 | 60 |
| Host | Mail server | TTL |
|---|---|---|
| retty.me | 10 aspmx.l.google.com | 300 |
| retty.me | 20 alt1.aspmx.l.google.com | 300 |
| retty.me | 20 alt2.aspmx.l.google.com | 300 |
| retty.me | 30 aspmx2.googlemail.com | 300 |
| retty.me | 30 aspmx3.googlemail.com | 300 |
| retty.me | 30 aspmx4.googlemail.com | 300 |
| retty.me | 30 aspmx5.googlemail.com | 300 |
| Host | Name server | TTL |
|---|---|---|
| retty.me | ns-1431.awsdns-50.org | 21600 |
| retty.me | ns-1566.awsdns-03.co.uk | 21600 |
| retty.me | ns-177.awsdns-22.com | 21600 |
| retty.me | ns-845.awsdns-41.net | 21600 |
| Host | Text | TTL |
|---|---|---|
| retty.me | "dkim=unknown" | 300 |
| retty.me | "google-site-verification=_tgjrW9ZNMI8LQ-vr-CVnHbLMeFIe0C7el909KZ8gIU" | 300 |
| retty.me | "google-site-verification=jatHIEFz6P_Ei0uO2YhWkHXDeUUy4cA1cPSCewubFSA" | 300 |
| retty.me | "google-site-verification=q7GGQJnI6Ke7hpZjPbf7XioaMUPKilN9BBoherG4Xf8" | 300 |
| retty.me | "MS=ms45076872" | 300 |
| retty.me | "pardot998041=935fefe96c8d5f891fd43d52347c1fb2532be2e1388c42d1b2651659e24491ec" | 300 |
| retty.me | "v=DKIM1\; k=rsa\; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCiicrrihONWUNTYrPUgTzhib7Sw1nkl5AfmPqR/j88paSawYR2+cy970YxGNXguXy+KF3qAwtnRiI4dqwkNawPFA3wwF6jC8t0uR5mtUlcE0ccV86o0rh0c73WkHyL50TpfVJv93rhkrVNnujqg54j8P6qrHczGgI+6KoMPC3O9wIDAQAB" | 300 |
| retty.me | "v=spf1 include:mail.zendesk.com include:amazonses.com include:_spf.google.com include:aspmx.pardot.com ~all" | 300 |
| retty.me | "ZOOM_verify_arvwCy3SUn8YbBC0VQfaEZ" | 300 |
| Host | Start of authority | TTL |
|---|---|---|
| retty.me | ns-1431.awsdns-50.org awsdns-hostmaster.amazon.com 1 7200 900 1209600 86400 | 900 |
Other domains served from 151.101.130.133. Normal for shared hosting and CDNs.
No reviews yet. Used retty.me? 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.
WOT's community rates retty.me excellent for safety (82/100). Its SSL certificate expired on 21 May 2024. See Security →
retty.me is registered through GMO INTERNET, INC. The public WHOIS record shows the registrant’s details. See WHOIS →
The registration expired on 15 Apr 2025. See Overview →
retty.me was registered on 15 Apr 2011, making it 15 years old. See Overview →
retty.me is served from 4 IP addresses, mainly on AS54113 Fastly Inc. in United States of America. See Hosting →
We detected 2 technologies, including Google Analytics and jQuery. See Built with →
Raw registry data for retty.me. May be redacted by privacy services.
Domain Name: retty.me Registry Domain ID: Registrar WHOIS Server: whois.discount-domain.com Registrar URL: http://www.onamae.com Updated Date: 2021-09-21T16:15:59Z Creation Date: 2011-04-15T12:18:42Z Registrar Registration Expiration Date: 2025-04-15T00:18:42Z Registrar: GMO INTERNET, INC. Registrar IANA ID: 49 Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +81.337709199 Domain Status: ACTIVE Registry Registrant ID: Registrant Name: kazuya takeda Registrant Organization: Retty, Inc. Registrant Street: 1-4-1 Mita Registrant Street: Sumitomo Fudosan Azabu Juban building 3F Registrant City: Minato Ku Registrant State/Province: Tokyo Registrant Postal Code: 108-0073 Registrant Country: JP Registrant Phone: 03-6852-1286 Registrant Phone Ext: Registrant Fax: Registrant Fax Ext: Registrant Email: [email protected] Registry Admin ID: Admin Name: kazuya takeda Admin Organization: takeda kazuya Admin Street: 1-4-1 Mita Admin Street: Sumitomo Fudosan Azabu Juban building 3F Admin City: Minato Ku Admin State/Province: Tokyo Admin Postal Code: 108-0073 Admin Country: JP Admin Phone: 03-6852-1286 Admin Phone Ext: Admin Fax: Admin Fax Ext: Admin Email: [email protected] Registry Tech ID: Tech Name: GMO Internet, Inc. Tech Organization: GMO Internet, Inc. Tech Street: 26-1 Sakuragaoka Tech Street: Cerulean Tower Tech City: Shibuya-ku Tech State/Province: Tokyo Tech Postal Code: 150-8512 Tech Country: JP Tech Phone: 03-3464-8727 Tech Phone Ext: Tech Fax: Tech Fax Ext: Tech Email: [email protected] Name Server: ns-1431.awsdns-50.org Name Server: ns-1566.awsdns-03.co.uk Name Server: ns-845.awsdns-41.net Name Server: ns-177.awsdns-22.com DNSSEC: unsigned URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/ >>> Last update of WHOIS database: 2021-09-21T16:15:59Z <<< For more information on Whois status codes, please visit https://icann.org/epp
The first response from http://www.retty.me, before any redirect: caching, server and policy headers.
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with retty.me. 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.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.
When the site first appeared, and what has changed since.
We record what changes from the next time this report is refreshed.