gmt.io

#BDB5DDF5 · Safe
65 / 100
LegitPad · gmt.io — Report card
104.20.27.62 Valid HTTPS Updated

What we know about gmt.io

Whether you are vetting gmt.io for a transaction, a partnership or simple curiosity, the public-record summary below will save you a few searches.

Technical Information

IP Address104.20.27.62
Server LocationUnknown
ISP / ProviderUnknown
SSL Certificate Valid HTTPS
SSL IssuerWE1
Valid Until2026-09-02
RegistrarUnknown

Initial findings

Our automated probe of gmt.io returned a clean DNS answer pointing to Unknown, served by Unknown, with the TLS handshake responding OK.

HTTPS verdict

Our HTTPS probe to gmt.io concluded with: OK. Together with the registrar and hosting country, this forms the security side of the scorecard.

Registration history

gmt.io has existed for about ? years. Long-lived domains are usually associated with established projects, although age alone is not a guarantee of safety.

Where the data lives

Anything you submit to gmt.io is processed on servers located in Unknown. Choose to share data accordingly.

Risk perspective

Domains with the profile of gmt.io (age ? years, SSL OK, registrar Unknown, country Unknown) usually fall in the "safe" category in our automated scoring.

Verdict

Trust score: 65/100safe. This is an automated, technical-only verdict; treat it as one data point among many.

Frequently Asked Questions

What jurisdiction handles gmt.io?
GeoIP places gmt.io on a server in Unknown, with Unknown as the announced ISP/network.
Is gmt.io encrypted?
The HTTPS handshake returned: OK.
When was gmt.io registered?
gmt.io has existed for about ? years according to RDAP.
Who registered gmt.io?
According to RDAP data, gmt.io was registered through Unknown.
What goes into the gmt.io trust rating?
It combines domain age, SSL validity, registrar reputation and DNS health into a 0-100 number. It is fully automated and only reflects public technical signals.

This report is generated automatically from public technical signals. It is not legal or financial advice.