flamescans.org

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

HTTP 429SafeSSL: 60 days left5 years old

One re-check per domain each UTC day.

50

flamescans.org was registered on 26 Jan 2021 via NameCheap, Inc. and the registry expiry is 26 Jan 2027. WHOIS data came from RDAP at https://rdap.publicinterestregistry.org/rdap/domain/flamescans.org.

flamescans.org publishes 2 nameservers. DNSSEC is not signed.

flamescans.org has 1 IPv4 address (192.157.56.140). The geolocation database places 192.157.56.140 in Buffalo, United States.

The TLS certificate from YR1 is valid and has 60 days left (TLS 1.3).

Tech detection named Cowboy and Erlang. The fingerprints ran on the homepage that was already downloaded.

No safety warning was recorded for flamescans.org in the checks that ran.

Domain · RDAP/WHOIS

flamescans.org was registered on 26 Jan 2021 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.publicinterestregistry.org/rdap/domain/flamescans.org.

Registeredsince 26 Jan 2021
Created26 January 2021
Updated12 August 2026
Expires26 January 2027
RegistrarNameCheap, Inc.
Statusclient transfer prohibited
Nameserversns1.brainydns.com, ns2.brainydns.com
DNSSECno
Sourcehttps://rdap.publicinterestregistry.org/rdap/domain/flamescans.org

flamescans.org 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.brainydns.com is published for flamescans.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/flamescans.org.

Nameserver ns2.brainydns.com is published for flamescans.org in the registration record from https://rdap.publicinterestregistry.org/rdap/domain/flamescans.org.

DNS

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

A192.157.56.140
AAAA—
NSns1.brainydns.com, ns2.brainydns.com
MX—
SPFabsent
DMARCabsent
CAA—
Wildcardon
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 192.157.56.140 answers for flamescans.org at resolver 1.1.1.1:53.

A random label under flamescans.org also resolved, which means wildcard DNS is on.

Hosting and geo

flamescans.org is placed in Buffalo, United States by the local geolocation database (db-ip).

Address192.157.56.140
CountryUnited States
CityBuffalo
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for flamescans.org is valid, with 60 days left and 2 subject alternative names. Source: tls:443.

IssuerYR1
Subjectflamescans.org
Valid from2 October 2026
Valid until31 December 2026
Days left60
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: *.flamescans.org, flamescans.org.

Tech stack

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

  • Cowboy · Web servers
  • Erlang · Programming languages

Cowboy is filed under Web servers.

Erlang is filed under Programming languages.

On-page checks

The homepage returned HTTP 429 in 145 ms. The target title is 0 characters and the page has 0 H1 headings.

Status429
TTFB145 ms
Title length0 no
Quoted titlenone
Meta descriptionnone no
H1 count0
HSTSno no
CSPno
X-Frame-Options—
Robots meta—
Canonical—
Language—
Links0
Images0
Faviconno

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 flamescans.org is clear, and URLhaus is clear. Source: family DNS and local lists.

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

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 10 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 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: dns a changed from 172.241.213.97 to 192.157.56.140.
  • October 2026: geo city changed from empty to Buffalo.
  • October 2026: geo country changed from empty to United States.

Questions

Is flamescans.org 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 flamescans.org?

flamescans.org is placed in Buffalo, United States.

When does flamescans.org expire?

flamescans.org expires on 26 January 2027 according to https://rdap.publicinterestregistry.org/rdap/domain/flamescans.org.

Who owns flamescans.org?

The registry did not return a person or a company for flamescans.org. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..

Sources

  • RDAP source https://rdap.publicinterestregistry.org/rdap/domain/flamescans.org at 2026-10-30T15:02:16Z
  • DNS source 1.1.1.1:53 at 2026-10-30T15:02:16Z
  • TLS source tls:443 at 2026-10-30T15:02:16Z
  • HTTP source https://flamescans.org/ at 2026-10-30T15:02:16Z
  • Tech source wappalyzergo at 2026-10-30T15:02:16Z
  • Geo source db-ip at 2026-10-30T15:02:16Z
  • Safety source family DNS and local lists at 2026-10-30T15:02:16Z

Methodology

Related reports

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

.org NameCheap, 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.