Hostname

jyoungel.com

Last fetched Wed, 16 Sep 2026 00:25:07 GMT

jyoungel.com resolves to 147.79.79.48, announced in 147.79.79.0/24 by AS-HOSTINGER - Hostinger International Limited in US. jyoungel.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this: 0
Verdict coverage: known-clean

Nutrition Label

Resolution chain

147.79.79.48
147.79.79.0/24 · AS-HOSTINGER - Hostinger International Limited · Boston, US
15.197.225.128
15.197.224.0/20 · AMAZON-02 - Amazon.com, Inc. · Montreal, CA
2.57.91.204
2.57.91.0/24 · AS-HOSTINGER - Hostinger International Limited · Asheville, US
3.33.251.168
3.33.240.0/20 · AMAZON-02 - Amazon.com, Inc. · Montreal, CA
84.32.84.179
84.32.84.0/24 · AS-HOSTINGER - Hostinger International Limited · Vilnius, LT
88.223.87.117
88.223.87.0/24 · AS-HOSTINGER - Hostinger International Limited · Boston, US
92.113.16.82
92.113.16.0/21 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
92.113.23.80
92.113.16.0/21 · AS-HOSTINGER - Hostinger International Limited · Frankfurt am Main, DE
88.222.222.172
88.222.222.0/24 · AS-HOSTINGER - Hostinger International Limited · Vilnius, LT
2.57.91.12
2.57.91.0/24 · AS-HOSTINGER - Hostinger International Limited · Vilnius, LT
88.222.222.174
88.222.222.0/24 · AS-HOSTINGER - Hostinger International Limited · Vilnius, LT
88.222.222.29
88.222.222.0/24 · AS-HOSTINGER - Hostinger International Limited · Vilnius, LT

IPv6 resolution

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar: iana:146

Subdomains

Subdomain
books.jyoungel.com

Showing 1 of 1 subdomain (1 per page).

Mail and authentication

Nameservers

sureena.ns.cloudflare.com
yoxall.ns.cloudflare.com
ns75.domaincontrol.com
ns76.domaincontrol.com
solar.dns-parking.com
lunar.dns-parking.com

MX records

mx1.hostinger.com
mx2.hostinger.com

Threat-feed evidence

History

Pivot from jyoungel.com into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "jyoungel.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.