2torme.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
70
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
70
2torme.com was registered on 15 Aug 2019 via Squarespace Domains II LLC and the registry expiry is 15 Aug 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/2torme.com.
2torme.com publishes 3 nameservers. DNSSEC is not signed.
2torme.com has 1 IPv4 address (40.160.24.203). The geolocation database places 40.160.24.203 in Reston, United States.
The TLS certificate from YR2 is valid and has 52 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Elementor, LiteSpeed, LiteSpeed Cache, Litespeed Cache, MySQL, PHP and WordPress. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for 2torme.com in the checks that ran.
2torme.com was registered on 15 Aug 2019 via Squarespace Domains II LLC. The registry returned 2 status values and 3 nameservers from https://rdap.verisign.com/com/v1/domain/2torme.com.
| Registered | since 15 Aug 2019 |
|---|---|
| Created | 15 August 2019 |
| Updated | 31 July 2026 |
| Expires | 15 August 2027 |
| Registrar | Squarespace Domains II LLC |
| Status | client delete prohibited, client transfer prohibited |
| Nameservers | ns1.serverhostgroup.com, ns2.serverhostgroup.com, ns3.serverhostgroup.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/2torme.com |
2torme.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.
2torme.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 ns1.serverhostgroup.com is published for 2torme.com in the registration record from https://rdap.verisign.com/com/v1/domain/2torme.com.
Nameserver ns2.serverhostgroup.com is published for 2torme.com in the registration record from https://rdap.verisign.com/com/v1/domain/2torme.com.
Nameserver ns3.serverhostgroup.com is published for 2torme.com in the registration record from https://rdap.verisign.com/com/v1/domain/2torme.com.
2torme.com has 1 address record, 1 mail exchanger and 3 nameservers, measured at 1.1.1.1:53.
| A | 40.160.24.203 |
|---|---|
| AAAA | — |
| NS | ns1.serverhostgroup.com, ns2.serverhostgroup.com, ns3.serverhostgroup.com |
| MX | 2torme.com (0) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at 2torme.com is "v=spf1 ip4:40.160.24.203 include:relay.mailchannels.net +a +mx +ip4:45.56.79.157 ~all".
IPv4 address 40.160.24.203 answers for 2torme.com at resolver 1.1.1.1:53.
Mail exchanger 2torme.com has preference 0.
2torme.com is placed in Reston, United States by the local geolocation database (db-ip).
| Address | 40.160.24.203 |
|---|---|
| Country | United States |
| City | Reston |
| Source | db-ip |
The certificate for 2torme.com is valid, with 52 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YR2 |
|---|---|
| Subject | *.2torme.com |
| Valid from | 23 September 2026 |
| Valid until | 22 December 2026 |
| Days left | 52 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.2torme.com, 2torme.com.
Tech detection checked the fetched homepage and named 7 products. Source: wappalyzergo.
Elementor is filed under Page builders, WordPress plugins.
LiteSpeed is filed under Web servers.
LiteSpeed Cache is filed under Caching, WordPress plugins.
Litespeed Cache is filed under Caching, WordPress plugins.
MySQL is filed under Databases.
PHP is filed under Programming languages.
WordPress is filed under CMS, Blogs.
The homepage returned HTTP 200 in 309 ms. The target title is 6 characters and the page has 2 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 309 ms |
| Title length | 6 yes |
| Quoted title | "2torme" |
| Meta description | none no |
| H1 count | 2 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | noindex, nofollow |
| Canonical | https://www.2torme.com/ |
| Language | en-US |
| Links | 24 |
| Images | 4 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Family DNS for 2torme.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.
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 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.
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
2torme.com is placed in Reston, United States.
2torme.com expires on 15 August 2027 according to https://rdap.verisign.com/com/v1/domain/2torme.com.
The registry did not return a person or a company for 2torme.com. RDAP often redacts the registrant. The registrar on file is Squarespace Domains II LLC.
No other indexable reports share this TLD, host, or registrar yet.
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.
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.