svrforum.com

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

Online · 200SafeSSL: 71 days left5 years oldTranco #254138

One re-check per domain each UTC day.

85

svrforum.com was registered on 22 Dec 2020 via Cloudflare, Inc. and the registry expiry is 22 Dec 2026. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/svrforum.com.

svrforum.com publishes 2 nameservers. DNSSEC is signed.

svrforum.com has 1 IPv4 address (211.51.194.137). The geolocation database places 211.51.194.137 in Seocho (Seocho-dong), South Korea.

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

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

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

Domain · RDAP/WHOIS

svrforum.com was registered on 22 Dec 2020 via Cloudflare, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/svrforum.com.

Registeredsince 22 Dec 2020
Created22 December 2020
Updated22 November 2025
Expires22 December 2026
RegistrarCloudflare, Inc.
Statusclient transfer prohibited
Nameserverscarlos.ns.cloudflare.com, celine.ns.cloudflare.com
DNSSECyes
Sourcehttps://rdap.verisign.com/com/v1/domain/svrforum.com

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

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

DNS

svrforum.com has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.

A211.51.194.137
AAAA—
NScarlos.ns.cloudflare.com, celine.ns.cloudflare.com
MX—
SPFabsent
DMARCabsent
CAA—
Wildcardoff
DNSSECsigned
Resolver1.1.1.1:53

IPv4 address 211.51.194.137 answers for svrforum.com at resolver 1.1.1.1:53.

Hosting and geo

svrforum.com is placed in Seocho (Seocho-dong), South Korea by the local geolocation database (db-ip).

Address211.51.194.137
CountrySouth Korea
CitySeocho (Seocho-dong)
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for svrforum.com is valid, with 71 days left and 3 subject alternative names. Source: tls:443.

IssuerYR1
Subjectsvrforum.com
Valid from12 October 2026
Valid until10 January 2027
Days left71
SAN count3
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: svrforum.com, test.svrforum.com, www.svrforum.com.

Tech stack

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

  • HSTS · Security
  • Nginx · Web servers, Reverse proxies

HSTS is filed under Security.

Nginx is filed under Web servers, Reverse proxies.

On-page checks

The homepage returned HTTP 200 in 200 ms. The target title is 34 characters and the page has 1 H1 heading.

Status200
TTFB200 ms
Title length34 yes
Quoted title"Security Check - Nginx Proxy Guard"
Meta descriptionnone no
H1 count1
HSTSyes yes
CSPyes
X-Frame-OptionsSAMEORIGIN
Robots meta—
Canonical—
Languageen
Links1
Images1
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 svrforum.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
CSPyes

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 15 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 Seocho (Seocho-dong).
  • October 2026: geo country changed from empty to South Korea.

Questions

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

svrforum.com is placed in Seocho (Seocho-dong), South Korea.

When does svrforum.com expire?

svrforum.com expires on 22 December 2026 according to https://rdap.verisign.com/com/v1/domain/svrforum.com.

Who owns svrforum.com?

The registry did not return a person or a company for svrforum.com. RDAP often redacts the registrant. The registrar on file is Cloudflare, Inc..

Sources

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

Methodology

Related reports

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

.com Cloudflare, Inc.

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.