Homeβ€Ί Personal Blogβ€Ί atgreen.github.io
This site failed important safety checks β€” please read this before going any further.
Be careful β€” Dangerous

No β€” atgreen.github.io doesn't look safe

10/ 100 trust score
Industry: Personal Blog Checked Jun 22, 2026 Personal Blog average: 70 28 signals
Check another site

In plain English

This site is essentially unreachable β€” it returns a 404 error and has no identifiable owner, no web history, and no way to contact anyone behind it. Even if the technical security is fine, there is nothing here to trust because there is nothing here at all.

What you should do now

Don't panic. These steps limit the damage, and the sooner you take them the better.

1

Don't enter any details

No passwords, card numbers or personal information β€” even if the site looks professional.

2

Close the tab

Especially if you got here from an email, text message or social media ad.

3

Already paid? Call your bank

Contact your bank or card provider right away. They can often stop or reverse a recent payment.

4

Warn others

Report the site and share this check with anyone who sent you the link.

N Partner pick
Better safe than sorry. Stay covered everywhere: NordVPN's Threat Protection blocks known scam sites before they load.
Try NordVPN β†’
Cross-referenced 28 live signals from Google Safe Browsing, VirusTotal, WHOIS and more on Jun 22, 2026. How we score β†’

Where the score comes from

We look at six areas. Here's how atgreen.github.io did in each.
85
Security

Modern TLS encryption, a valid certificate, and a configured Content Security Policy make this a technically secure connection despite being hosted on GitHub Pages. No blacklist or malware flags were detected.

10
Identity

The WHOIS query failed entirely, so there is no way to verify who owns this domain. Combined with a 404 page and no archived history, the entity behind this site is effectively invisible.

15
Reputation

The site has zero web presence β€” no Wayback Machine history, no Tranco ranking, and it currently serves a 404 error. There is no evidence of prior activity or reputation, good or bad.

10
Transparency

No contact info, no about page, no branding, and no visible purpose. A site that cannot be reached and provides no way to identify who runs it is fundamentally opaque.

65
Compliance

For a personal blog or hobby project β€” which is what a GitHub Pages 404 suggests β€” missing privacy policies and terms of service are normal. There is no sign of commercial activity that would trigger legal requirements.

45
Infrastructure

Fast CDN and quick load times point to decent hosting, but no email setup, no DNSSEC, and no sitemap are common for a small project. Nothing alarming here, but nothing impressive either.

What we checked

The 28 signals behind this report.
Security & Transport
Certificate Issuer
Let's Encrypt
Content Security Policy
Present
Google Web Risk
Clean
SSL Certificate
Valid
Security Headers
1 of 6
Server
GitHub.com
TLS Version
TLS 1.3
Identity & WHOIS
About Page
Not found
Branding
Missing
Business Disclosure
Not found
Contact Info
Not found
Legal Pages
Missing
Infrastructure & DNS
CDN
Fastly
DNS Blacklists
Clean
DNS Resolution
8 IP(s)
DNSSEC
Not enabled
Email (MX Records)
None
Page Load Time
172ms
Reputation & Reach
Page Heading
404
Page Title
Site not found Β· GitHub Pages
Sitemap
Not found
Social Media Presence
1 platforms
Structured Data
None found
Tranco Rank
Not ranked
Trustpilot
No Trustpilot profile
Web Archive History
No archive found
Website Status
HTTP 404
robots.txt
Not found

Think this verdict is wrong?

Site owners can request a fresh scan. Scores update automatically as signals change.

Report this site

What do you do when a website doesn't actually exist? That is essentially the situation with atgreen.github.io. Right now, this GitHub Pages subdomain serves a standard 404 page β€” there is no content, no business, no blog, and nothing to evaluate. The domain has no archived history in the Wayback Machine, and the WHOIS lookup failed, so we cannot even say who registered it or when.

For context, most personal blogs or small projects hosted on GitHub Pages have at least some content, a contact method, or a social media link. This site has none of those. It is not that there are red flags pointing to a scam; it is that there is no evidence the site was ever functional. The technical infrastructure (TLS, CDN) works fine, but that is like a locked storefront with an empty building behind it.

If you came across this URL from a link or an ad, be cautious β€” there is no way to verify what the site was supposed to be or who put it there. Without a working page, an owner, or any history, the safest assumption is to avoid it entirely.

More Personal Blog sites

How similar sites score. See all β†’