gpblog.com

#7DE707FF · Very Safe
95 / 100
ScoreVivid · gpblog.com — Report card
104.26.13.37 Valid HTTPS 21.4 years Register SPA Updated

gpblog.com safety overview

Public records for gpblog.com stretch back about 21.4 years. Combined with the live SSL status, they form the basis of our trust score.

Technical Information

IP Address
104.26.13.37
Server Location
Unknown
ISP / Provider
Unknown

SSL Certificate

SSL Certificate
Valid HTTPS
SSL Issuer
WE1
Valid Until
2026-08-15

Registrar

Registrar
Register SPA
Registered On
2005-01-25
Expires On
2027-01-25
Domain Age
21.4 years

Public-record summary

From the public records linked to gpblog.com we extracted four anchors: country Unknown, registrar Register SPA, age 21.4 yrs, encryption status OK. Everything else builds on those.

How long has gpblog.com existed?

According to RDAP records, gpblog.com was registered around 21.4 years ago through Register SPA. This is a useful signal but should be combined with content review.

In-transit protection

For data moving between the user and gpblog.com, the encryption check returned: OK. This is the single most important infrastructural safety check we run.

Infrastructure provider

Our GeoIP lookup places gpblog.com on the Unknown network, geographically in Unknown. ISP-level reputation matters: established networks tend to act on abuse reports faster.

How we read this profile

For gpblog.com, the combined picture (21.4 yrs, SSL OK, Unknown hosting, Register SPA registration) lands in the "very_safe" band. That is a starting point, not a final verdict.

Final take

Combining all signals, we rate gpblog.com at 95/100 (very_safe). Always perform your own due diligence before sharing personal data or money.

Frequently Asked Questions

Where was gpblog.com bought?
According to RDAP data, gpblog.com was registered through Register SPA.
What goes into the gpblog.com 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.
Is the WHOIS information about gpblog.com hidden?
Registrants increasingly use WHOIS privacy services. The registrar and registration date remain visible, which is what we use.
Is gpblog.com on a security blocklist?
No automatic blocklist hits were registered for gpblog.com during this check. Refresh the report to recheck.
Is gpblog.com a phishing website?
Our scanner does not perform visual similarity checks. We can only confirm that no obvious infrastructure markers (cert mismatch, fresh registration with high traffic) were triggered.

What looks good

  • Stable IPv4 hosting
  • Public RDAP record available
  • TLS supports modern cipher suites
  • Stable name-servers across NS records

What to watch

  • Technical signals alone cannot prove ownership
  • Privacy-protected WHOIS — operator not directly visible
  • Registrar based outside the target audience country

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

Vet your next domain in under 10 seconds.

No signup. No credit card. No hidden quotas.

Start a free check →