Report ID: #02E53587

corridor.dev

United States Valid HTTPS 1.4 years Updated
83
Very Safe
InspectTrust · corridor.dev — Report card
InspectTrust · corridor.dev

Vet your next domain in under 10 seconds.

No signup. No credit card. No hidden quotas.

Start a free check →

corridor.dev — independent inspection

Below: every public infrastructure fact our scanner could find on corridor.dev, mapped onto an objective 0-100 score.

IP Address · Server Location

216.150.1.1
United States

SSL Certificate

Valid HTTPS
R13
Valid Until: 2026-08-15

Registrar

Namecheap Inc.
Registered On: 2025-01-15
1.4 years

Very Safe

83/100
Verdict at a glance

Public-record summary

From the public records linked to corridor.dev we extracted four anchors: country United States, registrar Namecheap Inc., age 1.4 yrs, encryption status OK. Everything else builds on those.

How long has corridor.dev existed?

According to RDAP records, corridor.dev was registered around 1.4 years ago through Namecheap Inc.. This is a useful signal but should be combined with content review.

In-transit protection

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

Infrastructure provider

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

How we read this profile

For corridor.dev, the combined picture (1.4 yrs, SSL OK, United States hosting, Namecheap Inc. registration) lands in the "very_safe" band. That is a starting point, not a final verdict.

Final take

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

What looks good

  • Returns valid SOA and TXT records
  • Registered with an established registrar
  • Consistent name-server configuration
  • WHOIS data accessible (privacy-protected or full)

What to watch

  • Reputation data is limited to public sources
  • Uses generic shared hosting (cannot identify operator from IP)
  • TXT records expose minimal trust hints

Frequently Asked Questions

Does corridor.dev have IPv6?
Our DNS lookup returns AAAA-record presence as part of the report. If absent, corridor.dev is currently IPv4-only.
When was corridor.dev's certificate last checked?
SSL data on corridor.dev is recomputed on every refresh. The summary box at the top shows the timestamp of the latest probe.
Is corridor.dev safe for online payments?
Infrastructure check returned SSL OK and a "very_safe" score. This is a baseline; never enter card data on a site you have not verified through other channels.
What lowered corridor.dev's score?
corridor.dev sits at the lower band when at least one of these is true: SSL OK is failing, age 1.4 years is short, registrar Namecheap Inc. is unknown, or country United States does not match the audience.
Is corridor.dev trustworthy as a real business?
No automatic scam markers were detected, but a clean technical record is not a guarantee. Combine this report with your own judgement.

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