Hostname
jewelryvortex.com
Last fetched
jewelryvortex.com resolves to 18.244.18.27, announced in 18.244.16.0/21 by AMAZON-02 - Amazon.com, Inc. in DE. jewelryvortex.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 18.244.18.27
18.244.16.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.244.18.48
18.244.16.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.244.18.85
18.244.16.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.244.18.87
18.244.16.0/21 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.67.181.15
18.67.181.0/24 · AMAZON-02 - Amazon.com, Inc. · Kuala Lumpur, MY
- 18.67.181.24
18.67.181.0/24 · AMAZON-02 - Amazon.com, Inc. · Kuala Lumpur, MY
- 18.67.181.33
18.67.181.0/24 · AMAZON-02 - Amazon.com, Inc. · Kuala Lumpur, MY
- 18.67.181.5
18.67.181.0/24 · AMAZON-02 - Amazon.com, Inc. · Kuala Lumpur, MY
- 3.160.107.18
3.160.107.0/24 · AMAZON-02 - Amazon.com, Inc. · Buenos Aires, AR
- 3.160.107.21
3.160.107.0/24 · AMAZON-02 - Amazon.com, Inc. · Buenos Aires, AR
- 3.160.107.87
3.160.107.0/24 · AMAZON-02 - Amazon.com, Inc. · Buenos Aires, AR
- 3.160.107.95
3.160.107.0/24 · AMAZON-02 - Amazon.com, Inc. · Buenos Aires, AR
IPv6 resolution
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:228
- Registrant organisation
- moniker privacy services
- Contact emails
- info@xjewelryx.com, jewelryvortex.com@monikerprivacy.net, 1387b345e9ca7d50508a1a5ab805671b6c5b9fa42d05011a67f0938874d9c40f@jewelryvortex.com.whoisproxy.org, 358709681439f3784f9b6739949b979b5840417f3729e720b2721d408553a7e2@jewelryvortex.com.whoisproxy.org, 3b3edca99430463a4f0f55b1b68c68a985cb81977e565871f735ce0297794f26@jewelryvortex.com.whoisproxy.org, 3d03adee12440395efb982e8ef693dd9245c37b84cd5857db083ea35961f011b@jewelryvortex.com.whoisproxy.org, 3f4f12291062be4bc8ee0fb11e721797135a031ca4a8af424b1fdf2375f275ff@jewelryvortex.com.whoisproxy.org, 45506cdd67674b39bb85033f357cf6981f600c33405ff29d4574d12dd26497a6@jewelryvortex.com.whoisproxy.org, 4e57f371f55a24ad3440979ae16fb4c14668a83332400cd0eeb692b08004f2dc@jewelryvortex.com.whoisproxy.org, 5210a7761cad3e6f184accf7907ec742c001220255ba794e8dd8450c5e725614@jewelryvortex.com.whoisproxy.org, 55d60eeef17fa49dfae0c16667b9a96e5126fbb5d6648b3b2fc895bcc2a79ff9@jewelryvortex.com.whoisproxy.org, 57de4b13aaba68e32fe8a4fd2b1b49144dcc6bbd43ba4c5e0a37671106e64dda@jewelryvortex.com.whoisproxy.org, 5b0fac64bd66de6df99b53a45227eca8176c568457bc1d9e571439ab2f6ebb0f@jewelryvortex.com.whoisproxy.org, 6320f8422ecb3fda9bb849d880ea0e0a2c4449fb8a0f4c6eb6c5a0b0c4f046d9@jewelryvortex.com.whoisproxy.org, 6e92036a95e79b12f2c02ce51f4c622d54034073b17c24f77e3b54214e0339b1@jewelryvortex.com.whoisproxy.org, 7132489217012c6dca33b9a2192a58e8983f1554eec75a9f87153ac4bca42f19@jewelryvortex.com.whoisproxy.org, 8be496037207e78522135f10b104522b3154d4c4f1cd0c657639c070bb8a98e6@jewelryvortex.com.whoisproxy.org, 8bfe56b987bb44718fce76ecf2323d9f025be9d9e3ca7cd6082259af7fead2e4@jewelryvortex.com.whoisproxy.org, 961d6acca4c69333b35dc7d46e81561bc8a87ee04d19426a764610702d1ba607@jewelryvortex.com.whoisproxy.org, acd7ddb412a6cb58a3c0a5f76a632a2e9103ec39c122d1c8bd51232866978287@jewelryvortex.com.whoisproxy.org and 6 more
Subdomains
Showing 2 of 2 subdomains (2 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- ns-326.awsdns-40.com
- ns-531.awsdns-02.net
- ns-1197.awsdns-21.org
- ns-1985.awsdns-56.co.uk
MX records
- mailstore1.secureserver.net
- smtp.secureserver.net
Threat-feed evidence
History
Related pages
Pivot from jewelryvortex.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: "jewelryvortex.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.