Website reputation report

writingdeveloper.blog

Last checked 1 week ago · Point-in-time assessment

75/100Technical Safety ScoreIndependent technical assessment, not a visitor rating
Would you recommend this page? No community votes yet 0/0 Your vote is for this page in this report only—not the entire website. No account required · One vote per browser.
Captured homepage of writingdeveloper.blog in the current scan
Website screenshot from the current report

Share report

● Evidence is limited

What is this website?

로스앤젤레스의 AI 네이티브 제품 엔지니어이자 전 CTO 이시형. 개발자 도구, Applied AI, 풀스택 제품, 로컬 GPU 인프라와 그 안의 엔지니어링 판단을 기록합니다.

No listed local patterns observedHomepage-only analysis is not a malware clearance. Read the scope and findings below.

75/100Safety Score
75%Evidence Confidence
Trust Radar evidence profile Eight evidence dimensions from zero to one hundred. Exact values surround the chart. Threat Intelligence55 Domain History84 Infrastructure92 Website Security95 Security Hygiene80 Transparency52 Reputation50 Operational Stability84
Trust RadarEight observed factors. Select one to inspect its evidence.

How to read this report

Safety Score evaluates observed signals. Evidence Confidence measures how complete, direct, fresh, and consistent those signals are.

No automated scan can guarantee that a website is safe.

Current report context

What changed since the last scan

  • No earlier report to compare
What this scan could verify · 6 observed, 0 unavailable
DNS observed
Registration lookup observed
Network observed
TLS observed
Website response observed
Website content observed

Unavailable and unperformed checks are not clean results. The detailed evidence below remains the source for each conclusion.

Report an inaccuracy in this report →

Independent evidence brief

What we observed about writingdeveloper.blog

Updated Oct 6, 2026

The latest scan examined 10 public pages on writingdeveloper.blog. Website descriptions below come from the site itself. Registration, connection and threat findings were checked separately.

Purpose and visible content

On its About page, the site says: 로스앤젤레스의 AI 네이티브 제품 엔지니어이자 전 CTO 이시형. 개발자 도구, Applied AI, 풀스택 제품, 로컬 GPU 인프라와 그 안의 엔지니어링 판단을 기록합니다.

Registrar and domain history

Registered on Oct 5, 2019. Registrar: Automattic Inc..

Recorded expiry date: Oct 5, 2028. Registry data can change.

Connection and hosting evidence

The checked homepage returned HTTP 200 in about 2000 ms.

A valid TLS certificate was observed, expiring Nov 27, 2026.

Threat checks and score context

External malware-provider coverage was unavailable. The report does not treat this missing check as a clean result.

Safety Score: 75/100. Evidence Confidence: 75%. These measure different things.

Community reviews of writingdeveloper.blog

No approved reviews yet ☆☆☆☆☆

Visitor experiences are separate from the independent technical Safety Score.

Visitor opinions remain separate from the technical Safety Score.

Public content profile

Pages reviewed on writingdeveloper.blog

10 of up to 10 pages

We sampled public pages from this website to understand its subject and contact paths. The titles and short descriptions below come from the website itself. They are not endorsements or independent safety findings.

이시형 - AI 네이티브 제품 엔지니어 | WritingDeveloper로스앤젤레스의 AI 네이티브 제품 엔지니어 이시형. 개발자 도구, RAG 시스템, 로컬 AI/GPU 인프라, 프로덕션 풀스택 제품을 직접 구축·운영합니다. 이시형 · AI 네이티브 제품 엔지니어 & 시니어 풀스택 | WritingDeveloper로스앤젤레스의 AI 네이티브 제품 엔지니어이자 전 CTO 이시형. 개발자 도구, Applied AI, 풀스택 제품, 로컬 GPU 인프라와 그 안의 엔지니어링 판단을 기록합니다. JuiceBar 만들기: PC 전력을 전기요금으로 바꾸기 | WritingDeveloperWindows가 알려주는 것은 일부 부품의 전력이고, 제가 궁금한 것은 PC 전체가 이번 달 전기요금에 얼마를 보태는지였습니다. 측정할 수 있는 것은 측정하고, 나머지는 보정하며, 불확실성은 숨기지 않는 트레이 앱을 만들었습니다. 제 홈서버는 노트북입니다 | WritingDeveloperRTX 4080 노트북 한 대와 Oracle Cloud VM 하나를 Tailscale 사설망으로 묶어 생성 파이프라인과 내부 도구들을 직접 돌리고 있습니다. 무엇을 집에 두고 무엇을 클라우드에 뒀는지, 무엇을 공개하고 무엇을 잠갔는지 정리했습니다. 발모벽을 고치려고 만든 앱, 아직 못 고친 이야기 | WritingDeveloper손이 머리로 가는 걸 스스로 인지하지 못한다는 게 발모벽의 진짜 문제였습니다. 웹캠으로 그 순간을 잡아주는 앱 Don't Touch를 만들고, 쓰고, 방치하고, 한 통의 이메일을 받기까지의 정직한 기록입니다. 프로젝트 43개 · 웹·앱·게임·개발자 도구 | WritingDeveloper이시형이 직접 만든 프로젝트 43개. SaaS와 개발자 도구, 게임, AI 실험까지 라이브 데모·스토어 링크와 함께 정리했습니다. 프로젝트 묘지 · 실패에서 배운 것 | WritingDeveloper이시형이 만들었다 실패하거나 중단한 프로젝트들의 추모관. 각 묘비에는 사인(死因)과 정직한 회고, 배운 점을 담았습니다. 이시형 — 브라우저 자동화 · AI 통합 · 시니어 풀스택 | WritingDeveloper로스앤젤레스의 시니어 소프트웨어 엔지니어. Playwright/브라우저 자동화, 기존 제품 AI 통합, Next.js/PostgreSQL 프로덕션 시스템과 릴리스 QA를 수행합니다. 공개 데모·스토어가 있는 제품 19건. 탐험 | WritingDeveloper이시형의 포트폴리오를 인터랙티브 3D 공간에서 탐험해보세요. 프로젝트·스킬·타임라인·글을 실시간 WebGL로 둘러봅니다. Build Logs from Shipping Real Products | WritingDeveloperIn-depth build logs and dev stories from Sihyeong Lee — AI safety, full-stack architecture, indie hacking, and lessons from shipping real products.

Public page evidence

Topics and keywords observed on writingdeveloper.blog

7 phrases

These phrases were extracted locally from sampled public page metadata. They are observations, not search-volume or ranking estimates.

프로젝트Title, H1, Meta description3 sampled pages
ai 네이티브 제품Title, Meta description2 sampled pages
개발자 도구Title, Meta description3 sampled pages
엔지니어Title, Meta description3 sampled pages
제품 엔지니어Title, Meta description2 sampled pages
buildTitle, H1, Meta description2 sampled pages
로스앤젤레스의Meta description3 sampled pages

At a glance

Key findings

✓

Report is current

The displayed evidence comes from the published immutable scan.

i

Confidence is separate

Unavailable evidence is shown as missing and never counted as clean.

!

Verify before sensitive actions

Check the exact URL and context before payments, credentials, or downloads.

Fully explainable

Why this score?

Versioned weights
Threat IntelligenceWeight 25%
55/100

Threat providers were unavailable. The neutral uncertainty baseline is not a clean verdict.

Domain HistoryWeight 10%
84/100

Domain registration age and expiry were checked.

InfrastructureWeight 10%
92/100

Observed DNS records and network address were checked.

Website SecurityWeight 15%
95/100

Observed certificate validity and TLS protocol were checked.

Security HygieneWeight 15%
80/100

Observed security header values were checked for basic protective settings. Empty values, disabled HSTS and unrecognized values receive no credit. This is not a complete browser-policy validation.

TransparencyWeight 5%
52/100

Observed site metadata and About page were checked. Publisher-supplied details are not independently verified.

ReputationWeight 5%
50/100

Popularity is weak context, not proof of safety. Unranked sites use a neutral baseline.

Operational StabilityWeight 15%
84/100

Observed HTTP status and final connection scheme were checked.

Server-side analysis

Automated security checks

Local antivirus and phishing checks

ClamAV · homepage HTMLLocal antivirus is not enabled
Phishing.Database · exact hostnameLocal feed snapshot unavailable

Sampled scripts and pages

Resource antivirus is not enabled

0 resources checked · 13 script links observed on the homepage. Partial resource coverage.

ClamAV inspects the fetched homepage HTML on our server. New scans also sample up to four linked scripts and two collected internal pages, with size and time limits. Scripts are not executed. Other downloads, private server files and logged-in pages remain outside this check. A signature match needs investigation and can be a false positive. No match is not a whole-site safety guarantee.

Exact hostname lookup uses a downloaded Phishing.Database snapshot. It does not send this domain to an external lookup API or mark sibling subdomains as harmful. Not listed does not mean safe. Snapshot age is download age, not proof that every entry was recently revalidated.

Homepage HTML only · Eight local rule families · local-security-v2

Checks use the fetched page and redirect chain. Scripts are not executed, forms are not submitted, and linked files are not downloaded. This is not a malware clearance.

Page resource inventory

Linked scripts13
Inline scripts6
Embedded frames0
External script hosts0

Counts describe the sampled HTML, not every resource loaded by the browser. External resources are common and are not automatically harmful.

No listed local patterns observed. The limited rule set cannot detect every threat or behavior.

External threat intelligence

Provider coverageNot checked

Local checks do not query external reputation databases. An unavailable check is never a clean result.

Registration

Domain information

Public RDAP observation
Canonical domainwritingdeveloper.blog
RegistrarAutomattic Inc.
RegisteredOct 5, 2019
Domain age7 years
ExpiresOct 5, 2028
Registry statusesclient transfer prohibited
Report statePublished

Infrastructure

Network & hosting

Observed endpoint, not legal location
IP address216.150.1.193
Autonomous systemUnavailable
Network organizationUnavailable
Observed countryUnavailable
CDNNot detected
Web application firewallNot detected

At a glance

Infrastructure summary

Observed during this scan

A compact view of the connection, DNS and security surface. These observations describe what the scanner could verify at scan time and do not prove ownership or ongoing availability.

HTTP response200 · https://writingdeveloper.blog/
Endpoint216.150.1.193
NetworkUnavailable
CDN and WAFNot detected · Not detected
DNS surface16 records · 2 nameservers · 0 mail exchangers
Protection signals6 security headers · 4 technologies · DNSSEC unknown

Page telemetry

Observed page statistics

Safe metadata only

These counters describe the fetched response and sampled HTML. Script counts describe references in the markup, not a complete browser network log. Cookie counts cover observed response headers.

Response size132,575 bytes
HTTP check duration2,000 ms
Cookies observed1
Script resources13 · 0 external hosts
Frames and sampled checks0 frames · 0 resources checked

Encrypted transport

TLS certificate

Valid when observed
StatusValid when observed
ProtocolTLSv1.3
IssuercountryName=US, organizationName=Let's Encrypt, commonName=YR1
Valid fromAug 29, 2026
Valid untilNov 27, 2026
Certificate nameswritingdeveloper.blog

Resolution

DNS footprint

DNSKEY status unknown

DNSKEY presence does not verify the DNSSEC signature chain. Missing records can mean no record was returned or the lookup was unavailable.

A216.150.1.193TTL —
A216.150.16.193TTL —
NSkarsyn.ns.cloudflare.comTTL —
NStim.ns.cloudflare.comTTL —
CAA0 issue "comodoca.com"TTL —
CAA0 issue "digicert.com; cansignhttpexchanges=yes"TTL —
CAA0 issue "letsencrypt.org"TTL —
CAA0 issue "pki.goog; cansignhttpexchanges=yes"TTL —
CAA0 issue "sectigo.com"TTL —
CAA0 issue "ssl.com"TTL —
CAA0 issuewild "comodoca.com"TTL —
CAA0 issuewild "digicert.com; cansignhttpexchanges=yes"TTL —
CAA0 issuewild "letsencrypt.org"TTL —
CAA0 issuewild "pki.goog; cansignhttpexchanges=yes"TTL —
CAA0 issuewild "ssl.com"TTL —
TXTgoogle-site-verification=3NyJ3p5--urfWUlQuOrCJkD8Xwkn14dXu5gU6Cuzzj4TTL —

DNS observations · no external lookup API

Domain email protection

Exact-host SPF and DMARC observations help the owner investigate email impersonation risks. They are separate from website malware checks and do not change the Safety Score.

SPFNo matching record returned for this exact hostname
DMARCNo matching record returned for this exact hostname

What to do next

Review the records with your mail administrator. Inventory legitimate senders and test SPF and DKIM alignment before enforcing a stricter DMARC policy. Fix duplicate records and investigate overly permissive SPF rules.

This bounded check does not send email, probe SMTP, evaluate recursive SPF includes, verify DKIM signatures or apply organizational-domain DMARC inheritance. A missing subdomain record does not prove that no inherited protection exists. A DNS timeout is unknown, not an absent record. A policy record is not proof that messages authenticate successfully.

Responsible disclosure

security.txt

RFC 9116 observation

No readable security.txt file was observed at the standard locations. This is informational and is not evidence of malware.

Browser protections

Security headers

6 observed
content-security-policypresent default-src 'self'; script-src 'self' 'nonce-ODc5NTQwMmQtNmJiNS00YjUxLTlhNzYtMWU5ZDAzYmYyYTg5' https://giscus.app https://va.vercel-scripts.com https://pagead2.googlesyndication.com https://*.googlesyndication.com https://partner.googleadservices.com https://tpc.googlesyndication.com https://www.googletagmanager.com; style-src 'self' 'unsafe-inline' https://giscus.app; img-src 'self' data: https:; font-src 'self'; worker-src 'self' blob:; connect-src 'self' https://giscus.app https://vitals.vercel-insights.com https://va.vercel-scripts.com https://api.github.com https://cdn.jsdelivr.net/gh/lojjic/[email protected]/packages/data/ https://www.googletagmanager.com https://*.google-analytics.com https://analytics.google.com https://*.analytics.google.com https://www.google.com https://csi.gstatic.com https://pagead2.googlesyndication.com https://*.googlesyndication.com https://*.doubleclick.net https://*.adtrafficquality.google; frame-src https://giscus.app https://googleads.g.doubleclick.net https://tpc.googlesyndication.com https://*.googlesyndication.com https://*.doubleclick.net https://*.adtrafficquality.google https://www.google.com; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; object-src 'none'; upgrade-insecure-requests
permissions-policypresent camera=(), microphone=(), geolocation=()
referrer-policypresent strict-origin-when-cross-origin
strict-transport-securitypresent max-age=63072000; includeSubDomains; preload
x-content-type-optionspresent nosniff
x-frame-optionspresent DENY

Response headers

Cookie protections

Passive observation
Cookies observed1
Missing Secure1
Missing HttpOnly1
Missing SameSite0

Only cookie attribute counts are retained. Cookie names and values are never stored. These observations are not proof of compromise and do not independently change the Safety Score.

Detected stack

Technologies

Bootstrap 80% Google Analytics 94% Next.js 96% Tailwind CSS 72%

Versions are shown only when publicly exposed by the page or response headers. An observed version is not, by itself, proof of a vulnerability.

JavaScript library advisories

JavaScript advisory analysis could not be completed or no eligible script files were sampled. No clean result is implied.

Recommended maintenance checks

Next.jsKeep Next.js and its runtime dependencies current, especially when server-side rendering is enabled.

About this website

What the site says about itself

로스앤젤레스의 AI 네이티브 제품 엔지니어이자 전 CTO 이시형. 개발자 도구, Applied AI, 풀스택 제품, 로컬 GPU 인프라와 그 안의 엔지니어링 판단을 기록합니다.

View the site's About page ↗

This is publisher supplied information. The independent safety findings are shown separately.

Publisher supplied

Public contact details

These details were observed on the website, not independently verified as an active support channel.

Emailsihyeongdev@gmail.comSource: https://writingdeveloper.blog/

Structured facts

Website identity & response

Public page metadata
Page title이시형 - AI 네이티브 제품 엔지니어 | WritingDeveloper
First headingI build.I ship.I bury thedead.
Description로스앤젤레스의 AI 네이티브 제품 엔지니어 이시형. 개발자 도구, RAG 시스템, 로컬 AI/GPU 인프라, 프로덕션 풀스택 제품을 직접 구축·운영합니다.
Canonical URLhttps://writingdeveloper.blog
Final URLhttps://writingdeveloper.blog/
HTTP response200 · text/html; charset=utf-8 · 2000 ms
Languageko
Structured typesWebSite
Page page detectedhttps://writingdeveloper.blog/blog/building-juicebarAbout page detectedhttps://writingdeveloper.blog/about
1100% evidence confidence
1100% evidence confidence
1100% evidence confidence
1100% evidence confidence
Local headers.permissions payment restricted100% evidence confidence
1100% evidence confidence
Local headers.permissions usb restricted100% evidence confidence
1100% evidence confidence
1100% evidence confidence
ko100% evidence confidence
1100% evidence confidence
missing100% evidence confidence
1100% evidence confidence
Dns consistency.cname present100% evidence confidence
unavailable100% evidence confidence
Dns consistency.mail route count100% evidence confidence
2100% evidence confidence
16100% evidence confidence
1100% evidence confidence
Local cookies.cookies missing samesite100% evidence confidence
1100% evidence confidence
2100% evidence confidence
Local headers.cors credentials with wildcard100% evidence confidence
Local headers.cors present100% evidence confidence
Local headers.cors wildcard origin100% evidence confidence
1100% evidence confidence
1100% evidence confidence
1100% evidence confidence
Local headers.csp unsafe eval100% evidence confidence
1100% evidence confidence
Local headers.csp wildcard sources100% evidence confidence
1100% evidence confidence
63072000100% evidence confidence

Connection path

Redirect chain

0 recorded hops

No redirect hop was recorded for the sampled homepage.

Premium monitoring

Catch downtime and security changes automatically

Regular checks, availability history, and alert emails are reserved for Premium websites. Free reports remain point-in-time scans and do not create recurring server work.

Enable monitoring for this website

Compared with the previous scan

What changed

A comparison will appear after the next completed scan.

Explainable matching

Digital fingerprint

fingerprint-v1
steady-anchor-trace-912

Comparable components help find technically related websites. A match does not prove common ownership.

DnsHashed private comparison value
TechnologiesHashed private comparison value

Material changes only

Change history

Show change history

No meaningful changes recorded yet.

Website icon for writingdeveloper.blog

Visual evidence

Website screenshot

Screenshot of writingdeveloper.blog
Captured once in an isolated browser during this scan. Visual tint is an interface overlay. The original evidence is not duplicated.

For site owners

Show your verified trust report

Place this lightweight badge in your footer to show visitors an independent, dated WebsiteVirusScanner report. It can increase visitor confidence, but it never changes or guarantees the score.

Choose a badge style
Preview on your site
WebsiteVirusScanner trust badge preview

Use the current report link so visitors can verify the evidence. A badge is a transparency signal, not a paid ranking boost.

Questions about writingdeveloper.blog

FAQ

Still have questions? Contact us →
Is writingdeveloper.blog safe to visit?

The latest Safety Score is 75/100 with 75% Evidence Confidence. This is a point-in-time assessment of observed technical signals, not a guarantee. Check the exact address and avoid entering payment details if anything looks unusual.

Did the scan detect malware on writingdeveloper.blog?

External threat-provider coverage was unavailable for this scan, so malware status is unverified.

When was writingdeveloper.blog registered?

The public registry record shows Oct 5, 2019. Registration details may be privacy-protected or updated later.

Did writingdeveloper.blog have a valid TLS certificate?

The scanner observed a valid TLS certificate using TLSv1.3. A valid certificate alone does not establish that the site is safe.

How does writingdeveloper.blog describe itself?

The website's About page describes its purpose in the report above. This is publisher-supplied information and is separate from independent security findings.

Can a paid listing change this website's score?

No. Premium placement and owner-supplied pages are labelled separately. Technical evidence, the Safety Score and moderation decisions remain independent.

Share your experience with writingdeveloper.blog

Community reviews are moderated and remain separate from the technical Safety Score.

Write review →